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

View Problem - Process Solution

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

% Computer : n009.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:28 EDT 2023

% Result   : Unknown 108.49s 110.56s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.11  % Problem  : GRP652+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n009.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:00:38 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.09/6.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.09/6.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.09/6.10  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 12.35/12.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.35/12.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.35/12.52  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 18.71/18.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.71/18.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.71/18.91  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 24.83/24.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.83/24.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.83/24.89  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 29.61/29.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.61/29.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.61/29.83  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 36.27/36.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.27/36.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.27/36.81  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 43.16/44.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.16/44.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.16/44.35  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 50.10/51.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.10/51.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.10/51.67  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 57.07/58.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.07/58.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.07/58.98  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.74/64.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.74/64.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.74/64.04  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 68.77/71.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.77/71.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.77/71.52  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 108.43/110.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 108.43/110.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 108.43/110.05  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 108.49/110.56  Timeout
%------------------------------------------------------------------------------