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

View Problem - Process Solution

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

% Computer : n019.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:04 EDT 2023

% Result   : Unknown 110.84s 114.38s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.13  % Problem  : TOP025+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.14  % Command  : nanocop.sh %s %d
% 0.13/0.35  % Computer : n019.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 300
% 0.13/0.35  % DateTime : Thu May 18 20:05:02 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 6.24/6.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.24/6.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.24/6.23  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.97/13.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.97/13.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.97/13.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 19.02/19.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.02/19.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.02/19.59  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 25.37/26.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.37/26.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.37/26.25  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 30.03/30.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.03/30.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.03/30.70  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 38.81/39.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.81/39.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.81/39.92  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.80/47.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.80/47.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.80/47.46  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 53.15/55.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.15/55.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.15/55.16  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 60.34/62.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.34/62.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.34/62.24  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 64.93/66.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.93/66.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.93/66.96  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.11/74.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.11/74.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.11/74.70  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 77.68/80.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.68/80.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.68/80.39  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 83.45/86.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.45/86.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.45/86.81  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 110.77/113.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 110.77/113.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 110.77/113.81  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 110.84/114.38  Timeout
%------------------------------------------------------------------------------