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

View Problem - Process Solution

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

% Computer : n024.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:19 EDT 2023

% Result   : Unknown 95.54s 102.19s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : GRP621+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n024.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 02:01:11 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 5.65/5.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.65/5.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.65/5.65  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.28/11.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.28/11.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.28/11.96  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 16.77/18.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.77/18.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.77/18.09  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 22.53/24.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.53/24.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.53/24.52  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.35/28.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.35/28.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.35/28.97  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 32.08/34.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.08/34.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.08/34.88  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 37.76/41.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.76/41.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.76/41.12  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 43.49/47.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.49/47.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.49/47.39  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 49.19/53.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.19/53.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.19/53.57  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 53.00/58.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.00/58.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.00/58.03  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 58.67/63.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.67/63.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.67/63.90  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 64.47/70.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.47/70.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.47/70.34  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 70.26/76.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.26/76.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.26/76.50  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 95.49/101.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 95.49/101.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 95.49/101.44  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 95.54/102.19  Timeout
%------------------------------------------------------------------------------