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

View Problem - Process Solution

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

% Computer : n010.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:28:42 EDT 2023

% Result   : Unknown 99.19s 103.00s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : LAT298+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n010.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 14:26:16 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 6.13/6.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.13/6.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.13/6.10  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.96/12.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.96/12.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.96/12.21  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.93/18.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.93/18.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.93/18.45  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.83/24.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.83/24.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.83/24.67  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.74/28.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.74/28.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.74/28.99  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.73/35.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.73/35.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.73/35.08  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.68/41.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.68/41.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.68/41.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.70/47.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.70/47.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.70/47.54  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.65/53.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.65/53.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.65/53.76  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.66/58.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.66/58.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.66/58.08  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.47/64.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.47/64.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.47/64.02  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 67.37/70.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.37/70.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.37/70.25  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 73.10/76.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.10/76.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.10/76.33  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.17/102.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.17/102.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.17/102.07  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.19/103.00  Timeout
%------------------------------------------------------------------------------