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

View Problem - Process Solution

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

% Computer : n028.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:44 EDT 2023

% Result   : Unknown 99.08s 102.12s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : LAT305+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n028.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:24:38 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 6.08/6.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.08/6.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.08/6.08  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 12.10/12.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.10/12.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.10/12.39  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 18.05/18.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.05/18.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.05/18.42  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 23.97/24.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.97/24.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.97/24.73  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 28.10/29.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.10/29.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.10/29.19  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 34.14/35.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.14/35.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.14/35.20  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 40.06/41.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.06/41.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.06/41.34  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 45.90/47.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.90/47.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.90/47.48  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 51.91/53.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.91/53.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.91/53.89  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 55.95/58.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.95/58.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.95/58.14  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 61.80/64.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.80/64.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.80/64.10  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 67.52/70.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.52/70.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.52/70.22  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 73.46/76.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.46/76.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.46/76.69  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 99.04/101.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.04/101.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.04/101.64  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 99.08/102.12  Timeout
%------------------------------------------------------------------------------