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

View Problem - Process Solution

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

% Computer : n022.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:21 EDT 2023

% Result   : Unknown 94.69s 101.19s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.13  % Problem  : GRP627+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n022.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.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 300
% 0.13/0.35  % DateTime : Fri May 19 01:52:22 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 5.63/5.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.63/5.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.63/5.65  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.44/12.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.44/12.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.44/12.10  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 17.31/18.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.31/18.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.31/18.44  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 22.97/24.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.97/24.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.97/24.47  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.76/28.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.76/28.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.76/28.92  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 32.32/34.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.32/34.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.32/34.78  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 37.89/41.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.89/41.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.89/41.03  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 43.60/47.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.60/47.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.60/47.35  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 49.14/53.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.14/53.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.14/53.52  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 52.99/58.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.99/58.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.99/58.03  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 58.65/64.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.65/64.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.65/64.00  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 64.27/70.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.27/70.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.27/70.15  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 69.86/76.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.86/76.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.86/76.39  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 94.67/101.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.67/101.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.67/101.07  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 94.69/101.19  Timeout
%------------------------------------------------------------------------------