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

View Problem - Process Solution

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

% Computer : n021.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:06 EDT 2023

% Result   : Unknown 97.42s 102.12s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12  % Problem  : TOP033+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n021.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 20:03:02 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 6.05/6.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.05/6.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.05/6.01  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.04/12.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.04/12.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.04/12.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.75/18.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.75/18.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.75/18.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.38/24.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.38/24.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.38/24.41  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.29/29.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.29/29.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.29/29.03  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.15/35.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.15/35.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.15/35.00  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 38.95/41.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.95/41.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.95/41.17  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 44.79/47.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.79/47.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.79/47.41  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 50.58/53.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.58/53.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.58/53.66  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.52/58.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.52/58.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.52/58.11  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 60.48/64.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.48/64.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.48/64.18  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.29/70.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.29/70.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.29/70.27  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 71.99/76.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.99/76.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.99/76.41  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.35/101.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.35/101.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.35/101.52  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.42/102.12  Timeout
%------------------------------------------------------------------------------