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

View Problem - Process Solution

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

% Computer : n020.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:20 EDT 2023

% Result   : Unknown 94.71s 102.02s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12  % Problem  : GRP626+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n020.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Fri May 19 01:44:24 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 5.75/5.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.75/5.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.75/5.76  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.32/11.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.32/11.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.32/11.85  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 16.82/18.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.82/18.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.82/18.09  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 22.53/24.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.53/24.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.53/24.43  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.38/28.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.38/28.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.38/28.93  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 31.88/34.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.88/34.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.88/34.65  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 37.38/40.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.38/40.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.38/40.86  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 43.07/47.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.07/47.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.07/47.21  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 48.71/53.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.71/53.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.71/53.49  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 52.47/57.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.47/57.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.47/57.88  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 58.08/63.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.08/63.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.08/63.74  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 63.81/70.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.81/70.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.81/70.17  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 69.45/76.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.45/76.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.45/76.29  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 94.66/101.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.66/101.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.66/101.25  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 94.71/102.02  Timeout
%------------------------------------------------------------------------------