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

View Problem - Process Solution

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

% Computer : n010.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 107.36s 110.16s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : GRP642+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n010.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:29:16 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 7.27/7.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.27/7.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.27/7.26  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 14.40/14.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.40/14.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.40/14.40  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 21.51/21.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.51/21.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.51/21.74  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 28.67/29.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.67/29.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.67/29.02  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.34/33.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.34/33.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.34/33.87  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 40.30/41.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.30/41.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.30/41.19  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 46.58/47.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.58/47.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.58/47.94  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 52.64/53.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.64/53.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.64/53.84  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 58.67/60.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.67/60.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.67/60.04  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 62.68/64.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.68/64.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.68/64.35  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 68.63/70.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.63/70.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.63/70.36  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 74.58/76.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 74.58/76.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.58/76.52  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 80.49/82.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.49/82.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.49/82.74  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 107.30/109.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 107.30/109.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 107.30/109.12  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 107.36/110.16  Timeout
%------------------------------------------------------------------------------