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

View Problem - Process Solution

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

% Computer : n003.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 99.66s 101.93s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : GRP641+4 : TPTP v8.1.2. Released v3.4.0.
% 0.12/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n003.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Fri May 19 01:59:21 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 6.14/6.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.14/6.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.14/6.14  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 12.18/12.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.18/12.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.18/12.41  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 18.18/18.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.18/18.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.18/18.49  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 24.13/24.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.13/24.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.13/24.75  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 28.13/29.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.13/29.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.13/29.00  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.05/35.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.05/35.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.05/35.06  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 40.12/41.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.12/41.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.12/41.46  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 46.07/47.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.07/47.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.07/47.48  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 52.08/53.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.08/53.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.08/53.75  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 56.33/58.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.33/58.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.33/58.29  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 62.22/64.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.22/64.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.22/64.01  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 68.18/70.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.18/70.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.18/70.37  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 74.16/76.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 74.16/76.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.16/76.52  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 99.64/101.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.64/101.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.64/101.42  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 99.66/101.93  Timeout
%------------------------------------------------------------------------------