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

View Problem - Process Solution

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

% Computer : n002.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 94.21s 102.11s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : GRP633+4 : TPTP v8.1.2. Released v3.4.0.
% 0.00/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n002.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:57:26 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 5.74/5.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.74/5.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.74/5.74  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.26/11.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.26/11.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.26/11.82  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 16.96/18.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.96/18.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.96/18.32  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 22.54/24.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.54/24.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.54/24.23  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.19/28.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.19/28.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.19/28.68  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 31.78/34.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.78/34.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.78/34.71  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 37.43/40.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.43/40.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.43/40.94  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 42.82/47.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.82/47.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.82/47.05  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 48.51/53.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.51/53.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.51/53.41  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 52.24/57.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.24/57.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.24/57.85  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 57.90/63.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.90/63.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.90/63.83  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 63.40/69.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.40/69.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.40/69.93  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 69.10/76.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.10/76.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.10/76.28  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 94.15/101.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.15/101.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.15/101.25  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 94.21/102.11  Timeout
%------------------------------------------------------------------------------