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

View Problem - Process Solution

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

% Computer : n012.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:26 EDT 2023

% Result   : Unknown 112.61s 116.45s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.09/0.11  % Problem  : GRP646+4 : TPTP v8.1.2. Released v3.4.0.
% 0.09/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n012.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Fri May 19 01:43:10 EDT 2023
% 0.13/0.33  % CPUTime  : 
% 6.13/6.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.13/6.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.13/6.16  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 14.14/14.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.14/14.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.14/14.22  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 22.14/22.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.14/22.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.14/22.53  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 29.78/30.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.78/30.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.78/30.42  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.74/36.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.74/36.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.74/36.14  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 42.31/43.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.31/43.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.31/43.88  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 49.88/52.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.88/52.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.88/52.16  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 57.48/60.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.48/60.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.48/60.43  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 64.69/68.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.69/68.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.69/68.31  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 68.71/72.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.71/72.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.71/72.60  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 74.81/78.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 74.81/78.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.81/78.77  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 81.01/85.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.01/85.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.01/85.03  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 87.03/91.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 87.03/91.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 87.03/91.15  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 112.53/116.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 112.53/116.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 112.53/116.07  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 112.61/116.45  Timeout
%------------------------------------------------------------------------------