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

View Problem - Process Solution

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

% Computer : n011.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 95.53s 102.20s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.13  % Problem  : GRP623+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.14/0.35  % Computer : n011.cluster.edu
% 0.14/0.35  % Model    : x86_64 x86_64
% 0.14/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35  % Memory   : 8042.1875MB
% 0.14/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35  % CPULimit : 300
% 0.14/0.35  % WCLimit  : 300
% 0.14/0.35  % DateTime : Fri May 19 02:00:38 EDT 2023
% 0.14/0.35  % CPUTime  : 
% 5.79/5.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.79/5.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.79/5.81  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.59/12.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.59/12.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.59/12.10  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 17.39/18.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.39/18.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.39/18.41  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 23.08/24.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.08/24.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.08/24.42  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.80/28.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.80/28.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.80/28.93  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 32.55/34.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.55/34.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.55/34.85  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 38.06/40.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.06/40.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.06/40.93  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 43.54/47.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.54/47.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.54/47.16  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 49.22/53.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.22/53.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.22/53.58  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 53.29/58.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.29/58.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.29/58.26  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 58.93/63.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.93/63.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.93/63.93  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 64.63/70.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.63/70.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.63/70.19  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 70.25/76.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.25/76.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.25/76.38  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 95.51/101.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 95.51/101.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 95.51/101.42  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 95.53/102.20  Timeout
%------------------------------------------------------------------------------