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

View Problem - Process Solution

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

% Computer : n005.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:46 EDT 2023

% Result   : Unknown 97.69s 102.02s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.13  % Problem  : LAT311+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n005.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:32:12 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 6.10/6.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.10/6.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.10/6.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.04/12.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.04/12.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.04/12.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.83/18.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.83/18.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.83/18.35  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.88/24.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.88/24.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.88/24.75  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.81/29.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.81/29.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.81/29.03  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.76/35.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.76/35.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.76/35.12  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.74/41.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.74/41.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.74/41.39  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.76/47.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.76/47.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.76/47.61  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.78/53.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.78/53.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.78/53.87  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.57/57.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.57/57.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.57/57.99  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.16/63.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.16/63.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.16/63.84  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.76/70.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.76/70.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.76/70.06  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.66/76.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.66/76.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.66/76.56  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.64/101.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.64/101.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.64/101.06  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.69/102.02  Timeout
%------------------------------------------------------------------------------