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

View Problem - Process Solution

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

% Computer : n007.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 103.77s 110.23s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : GRP632+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n007.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:43:13 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 5.59/5.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.59/5.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.59/5.58  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.18/11.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.18/11.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.18/11.91  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 19.71/21.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.71/21.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.71/21.06  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.59/28.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.59/28.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.59/28.70  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 31.65/34.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.65/34.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.65/34.19  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 38.13/40.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.13/40.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.13/40.79  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 44.93/48.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.93/48.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.93/48.23  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 51.54/55.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.54/55.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.54/55.37  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 58.09/62.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.09/62.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.09/62.62  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 62.56/67.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 62.56/67.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 62.56/67.78  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 68.20/74.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.20/74.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.20/74.19  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 73.52/80.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.52/80.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.52/80.07  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 78.71/85.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.71/85.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.71/85.12  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 103.76/109.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 103.76/109.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 103.76/109.29  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 103.77/110.23  Timeout
%------------------------------------------------------------------------------