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

View Problem - Process Solution

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

% Computer : n016.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:23 EDT 2023

% Result   : Unknown 112.20s 114.38s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.12  % Problem  : GRP636+4 : TPTP v8.1.2. Released v3.4.0.
% 0.10/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n016.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Fri May 19 02:26:32 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 7.56/7.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.56/7.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.56/7.57  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 15.36/15.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.36/15.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.36/15.05  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 23.00/23.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.00/23.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.00/23.24  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 30.48/31.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.48/31.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.48/31.48  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 35.55/37.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.55/37.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.55/37.37  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 42.33/44.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.33/44.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.33/44.28  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 48.50/50.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.50/50.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.50/50.81  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 54.73/57.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.73/57.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.73/57.19  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.88/64.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.88/64.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.88/64.20  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 66.48/69.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.48/69.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.48/69.04  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 73.45/76.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.45/76.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.45/76.43  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 112.14/114.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 112.14/114.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 112.14/114.22  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 112.20/114.38  Timeout
%------------------------------------------------------------------------------