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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : TOP037+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:08 EDT 2023

% Result   : Unknown 98.05s 102.26s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : TOP037+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.14/0.34  % Computer : n021.cluster.edu
% 0.14/0.34  % Model    : x86_64 x86_64
% 0.14/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.34  % Memory   : 8042.1875MB
% 0.14/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.34  % CPULimit : 300
% 0.14/0.34  % WCLimit  : 300
% 0.14/0.34  % DateTime : Thu May 18 20:08:47 EDT 2023
% 0.14/0.34  % CPUTime  : 
% 6.08/6.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.08/6.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.08/6.03  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.02/12.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.02/12.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.02/12.27  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.84/18.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.84/18.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.84/18.41  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.64/24.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.64/24.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.64/24.63  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.51/29.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.51/29.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.51/29.01  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.51/35.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.51/35.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.51/35.12  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.26/41.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.26/41.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.26/41.20  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 44.98/47.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.98/47.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.98/47.35  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 50.93/53.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.93/53.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.93/53.81  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.85/58.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.85/58.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.85/58.13  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 60.82/64.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.82/64.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.82/64.25  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.75/70.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.75/70.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.75/70.48  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.58/76.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.58/76.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.58/76.60  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.97/101.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.97/101.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.97/101.58  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.05/102.26  Timeout
%------------------------------------------------------------------------------