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

View Problem - Process Solution

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

% Computer : n013.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:20 EDT 2023

% Result   : Unknown 107.50s 111.28s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.11  % Problem  : GRP624+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/0.11  % Command  : nanocop.sh %s %d
% 0.11/0.32  % Computer : n013.cluster.edu
% 0.11/0.32  % Model    : x86_64 x86_64
% 0.11/0.32  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.32  % Memory   : 8042.1875MB
% 0.11/0.32  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.11/0.32  % CPULimit : 300
% 0.11/0.32  % WCLimit  : 300
% 0.11/0.32  % DateTime : Fri May 19 02:01:40 EDT 2023
% 0.11/0.32  % CPUTime  : 
% 6.85/6.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.85/6.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.85/6.86  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 14.00/14.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.00/14.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.00/14.41  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 20.77/21.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.77/21.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.77/21.34  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 27.31/28.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.31/28.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.31/28.35  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 31.83/33.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.83/33.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.83/33.67  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 38.64/41.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.64/41.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.64/41.02  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 44.27/47.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.27/47.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.27/47.26  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 49.66/53.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.66/53.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.66/53.16  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 55.38/58.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.38/58.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.38/58.76  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 61.38/65.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.38/65.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.38/65.24  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 68.41/72.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.41/72.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.41/72.34  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 107.40/110.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 107.40/110.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 107.40/110.34  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 107.50/111.28  Timeout
%------------------------------------------------------------------------------