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

View Problem - Process Solution

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

% Computer : n028.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 105.89s 101.94s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.12  % Problem  : GRP644+4 : TPTP v8.1.2. Released v3.4.0.
% 0.10/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n028.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:19:23 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.43/6.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.43/6.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.43/6.49  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 12.68/12.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.68/12.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.68/12.49  Peak sizes were: global stack 127264 kbytes, trail stack 4192 kbytes
% 19.07/18.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.07/18.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.07/18.89  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 25.31/25.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.31/25.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.31/25.08  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 29.55/29.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.55/29.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.55/29.27  Peak sizes were: global stack 127264 kbytes, trail stack 4192 kbytes
% 35.70/35.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.70/35.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.70/35.27  Peak sizes were: global stack 127264 kbytes, trail stack 4192 kbytes
% 41.86/41.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.86/41.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.86/41.50  Peak sizes were: global stack 127264 kbytes, trail stack 4192 kbytes
% 48.18/47.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.18/47.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.18/47.86  Peak sizes were: global stack 127264 kbytes, trail stack 4192 kbytes
% 54.37/53.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.37/53.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.37/53.95  Peak sizes were: global stack 127264 kbytes, trail stack 4192 kbytes
% 58.44/58.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.44/58.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.44/58.11  Peak sizes were: global stack 127264 kbytes, trail stack 4192 kbytes
% 64.83/64.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.83/64.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.83/64.49  Peak sizes were: global stack 127264 kbytes, trail stack 4192 kbytes
% 71.04/70.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.04/70.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.04/70.70  Peak sizes were: global stack 127264 kbytes, trail stack 4192 kbytes
% 77.31/76.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.31/76.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.31/76.74  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 105.81/101.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 105.81/101.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.81/101.45  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 105.89/101.94  Timeout
%------------------------------------------------------------------------------