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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : GRP651+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:27 EDT 2023

% Result   : Unknown 104.10s 102.11s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : GRP651+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.14/0.34  % Computer : n013.cluster.edu
% 0.14/0.34  % Model    : x86_64 x86_64
% 0.14/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.34  % Memory   : 8042.1875MB
% 0.14/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.34  % CPULimit : 300
% 0.14/0.34  % WCLimit  : 300
% 0.14/0.34  % DateTime : Fri May 19 01:45:26 EDT 2023
% 0.14/0.34  % CPUTime  : 
% 6.56/6.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.56/6.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.56/6.57  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 13.06/12.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.06/12.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.06/12.79  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 19.46/19.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.46/19.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.46/19.00  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 25.77/25.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.77/25.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.77/25.08  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 29.86/29.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.86/29.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.86/29.19  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 36.22/35.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.22/35.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.22/35.57  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 42.73/41.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.73/41.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.73/41.81  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 48.96/47.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.96/47.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.96/47.87  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 55.11/53.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.11/53.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.11/53.98  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 59.16/58.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.16/58.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.16/58.18  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 65.28/64.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.28/64.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.28/64.40  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 71.76/70.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.76/70.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.76/70.89  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 78.24/77.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.24/77.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.24/77.14  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 104.01/101.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 104.01/101.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 104.01/101.92  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 104.10/102.11  Timeout
%------------------------------------------------------------------------------