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

View Problem - Process Solution

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

% Computer : n009.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:43 EDT 2023

% Result   : Unknown 105.11s 109.43s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.14/0.14  % Problem  : LAT299+4 : TPTP v8.1.2. Released v3.4.0.
% 0.14/0.15  % Command  : nanocop.sh %s %d
% 0.14/0.37  % Computer : n009.cluster.edu
% 0.14/0.37  % Model    : x86_64 x86_64
% 0.14/0.37  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.37  % Memory   : 8042.1875MB
% 0.14/0.37  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.37  % CPULimit : 300
% 0.14/0.37  % WCLimit  : 300
% 0.14/0.37  % DateTime : Thu May 18 13:53:52 EDT 2023
% 0.14/0.37  % CPUTime  : 
% 6.72/6.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.72/6.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.72/6.68  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 13.37/13.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.37/13.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.37/13.95  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 19.99/21.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.99/21.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.99/21.26  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 26.00/27.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.00/27.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.00/27.97  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 29.86/32.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.86/32.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.86/32.20  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 35.50/37.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.50/37.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.50/37.98  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 40.98/44.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.98/44.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.98/44.10  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 46.51/50.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.51/50.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.51/50.31  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 52.02/56.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.02/56.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.02/56.55  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 58.43/63.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.43/63.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.43/63.68  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 65.75/70.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.75/70.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.75/70.79  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 105.06/108.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 105.06/108.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 105.06/108.83  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 105.11/109.43  Timeout
%------------------------------------------------------------------------------