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

View Problem - Process Solution

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

% Computer : n010.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 103.38s 105.91s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : TOP036+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n010.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 19:58:47 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 5.91/5.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.91/5.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.91/5.95  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.91/12.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.91/12.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.91/12.33  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.01/18.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.01/18.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.01/18.59  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.89/24.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.89/24.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.89/24.61  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.79/29.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.79/29.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.79/29.02  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.75/34.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.75/34.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.75/34.99  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.26/40.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.26/40.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.26/40.90  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.58/47.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.58/47.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.58/47.87  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 52.65/54.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.65/54.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.65/54.80  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 56.76/59.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.76/59.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.76/59.11  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 64.33/66.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.33/66.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.33/66.65  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 103.35/105.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 103.35/105.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 103.35/105.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 103.38/105.90  Timeout
%------------------------------------------------------------------------------