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

View Problem - Process Solution

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

% Computer : n020.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:49 EDT 2023

% Result   : Unknown 98.24s 102.14s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : LAT324+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n020.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Thu May 18 14:17:07 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 6.07/6.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.07/6.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.07/6.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.02/12.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.02/12.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.02/12.23  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.90/18.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.90/18.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.90/18.48  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.77/24.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.77/24.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.77/24.67  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.74/29.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.74/29.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.74/29.01  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.66/35.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.66/35.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.66/35.12  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.59/41.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.59/41.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.59/41.34  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.49/47.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.49/47.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.49/47.57  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.46/53.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.46/53.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.46/53.83  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.40/58.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.40/58.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.40/58.11  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.35/64.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.35/64.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.35/64.23  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 67.24/70.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.24/70.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.24/70.37  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 73.11/76.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.11/76.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.11/76.64  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.14/101.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 98.14/101.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 98.14/101.29  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.24/102.14  Timeout
%------------------------------------------------------------------------------