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

View Problem - Process Solution

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

% Computer : n008.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:45 EDT 2023

% Result   : Unknown 99.23s 101.98s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : LAT309+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n008.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 : Thu May 18 14:20:59 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 6.07/6.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.07/6.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.07/6.06  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.13/12.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.13/12.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.13/12.37  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.08/18.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.08/18.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.08/18.48  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 24.09/24.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.09/24.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.09/24.75  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.09/29.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.09/29.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.09/29.08  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.15/35.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.15/35.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.15/35.23  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 40.16/41.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.16/41.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.16/41.37  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 46.19/47.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.19/47.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.19/47.54  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 52.06/53.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.06/53.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.06/53.73  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 56.02/58.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.02/58.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.02/58.03  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.90/64.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.90/64.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.90/64.05  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 67.82/70.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.82/70.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.82/70.27  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 73.74/76.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.74/76.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.74/76.50  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.21/101.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.21/101.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.21/101.51  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.23/101.98  Timeout
%------------------------------------------------------------------------------