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

View Problem - Process Solution

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

% Computer : n014.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:48 EDT 2023

% Result   : Unknown 99.07s 102.28s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.13  % Problem  : LAT323+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.35  % Computer : n014.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 300
% 0.13/0.35  % DateTime : Thu May 18 13:58:02 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 6.14/6.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.14/6.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.14/6.12  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.03/12.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.03/12.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.03/12.22  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.98/18.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.98/18.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.98/18.48  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.94/24.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.94/24.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.94/24.80  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.92/29.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.92/29.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.92/29.10  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.87/35.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.87/35.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.87/35.15  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.85/41.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.85/41.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.85/41.48  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.80/47.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.80/47.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.80/47.61  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.72/53.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.72/53.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.72/53.85  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.71/58.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.71/58.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.71/58.28  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 61.74/64.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.74/64.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.74/64.36  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 67.64/70.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.64/70.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.64/70.46  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 73.61/76.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.61/76.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.61/76.71  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.02/101.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.02/101.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.02/101.65  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 99.07/102.28  Timeout
%------------------------------------------------------------------------------