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

View Problem - Process Solution

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

% Computer : n032.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 11:16:25 EDT 2023

% Result   : Unknown 102.43s 101.33s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.09  % Problem  : GRP640+4 : TPTP v8.1.2. Released v3.4.0.
% 0.00/0.09  % Command  : nanocop.sh %s %d
% 0.09/0.28  % Computer : n032.cluster.edu
% 0.09/0.28  % Model    : x86_64 x86_64
% 0.09/0.28  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.09/0.28  % Memory   : 8042.1875MB
% 0.09/0.28  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.09/0.28  % CPULimit : 300
% 0.09/0.28  % WCLimit  : 300
% 0.13/0.28  % DateTime : Fri May 19 01:57:24 EDT 2023
% 0.13/0.28  % CPUTime  : 
% 6.32/6.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.32/6.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.32/6.38  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 12.73/12.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.73/12.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.73/12.63  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 18.92/18.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.92/18.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.92/18.66  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 25.11/24.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.11/24.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.11/24.89  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 29.22/28.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.22/28.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.22/28.97  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 35.50/35.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.50/35.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.50/35.19  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 41.71/41.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.71/41.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.71/41.37  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 47.96/47.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.96/47.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.96/47.54  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 54.21/53.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.21/53.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.21/53.84  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 58.32/57.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.32/57.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.32/57.90  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 64.58/64.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.58/64.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.58/64.14  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 70.67/70.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.67/70.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.67/70.08  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 76.93/76.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.93/76.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.93/76.51  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 102.38/101.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 102.38/101.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 102.38/101.25  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 102.43/101.33  Timeout
%------------------------------------------------------------------------------