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

View Problem - Process Solution

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

% Result   : Unknown 103.38s 103.02s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : GRP649+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n012.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 01:34:06 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.48/6.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.48/6.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.48/6.49  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 12.73/12.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.73/12.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.73/12.54  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 19.09/18.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.09/18.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.09/18.88  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 25.60/25.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.60/25.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.60/25.22  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 29.77/30.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.77/30.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.77/30.22  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 35.96/36.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.96/36.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.96/36.32  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 42.21/42.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.21/42.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.21/42.62  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 48.47/48.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.47/48.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.47/48.90  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 54.87/55.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.87/55.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.87/55.14  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 58.96/59.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.96/59.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.96/59.29  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 65.21/65.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.21/65.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.21/65.39  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 71.47/71.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.47/71.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.47/71.65  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 77.67/77.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.67/77.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.67/77.85  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 103.34/102.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 103.34/102.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 103.34/102.78  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 103.38/103.02  Timeout
%------------------------------------------------------------------------------