TSTP Solution File: TOP034+4 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : TOP034+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n027.cluster.edu
% Model    : x86_64 x86_64
% CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 2.10GHz
% Memory   : 8042.1875MB
% OS       : Linux 3.10.0-693.el7.x86_64
% CPULimit : 300s
% WCLimit  : 300s
% DateTime : Fri May 19 12:39:07 EDT 2023

% Result   : Unknown 97.09s 101.93s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : TOP034+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n027.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Thu May 18 20:25:10 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 5.89/5.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.89/5.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.89/5.95  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.84/12.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.84/12.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.84/12.19  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.57/18.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.57/18.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.57/18.25  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.32/24.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.32/24.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.32/24.52  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.17/28.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.17/28.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.17/28.91  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.07/34.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.07/34.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.07/34.98  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.06/41.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.06/41.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.06/41.39  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 44.86/47.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.86/47.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.86/47.33  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 50.65/53.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.65/53.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.65/53.62  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.58/58.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.58/58.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.58/58.03  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 60.33/63.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.33/63.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.33/63.84  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.13/70.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.13/70.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.13/70.22  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 71.92/76.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.92/76.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.92/76.34  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.08/101.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.08/101.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.08/101.17  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.09/101.93  Timeout
%------------------------------------------------------------------------------