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

View Problem - Process Solution

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

% Computer : n026.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:22 EDT 2023

% Result   : Unknown 96.42s 102.15s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : GRP631+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n026.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 02:01:57 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 5.86/5.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.86/5.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.86/5.85  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.56/12.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.56/12.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.56/12.01  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 17.24/18.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.24/18.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.24/18.22  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 22.86/24.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.86/24.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.86/24.45  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.80/29.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.80/29.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.80/29.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 32.63/34.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.63/34.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.63/34.93  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 38.36/41.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.36/41.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.36/41.15  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 44.02/47.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.02/47.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.02/47.31  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 49.66/53.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.66/53.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.66/53.57  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 53.61/58.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.61/58.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.61/58.18  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 59.41/64.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.41/64.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.41/64.08  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 64.86/69.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.86/69.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.86/69.97  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 70.25/76.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.25/76.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.25/76.14  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 96.40/101.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 96.40/101.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 96.40/101.22  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 96.42/102.15  Timeout
%------------------------------------------------------------------------------