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

View Problem - Process Solution

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

% Computer : n002.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 98.66s 102.07s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : LAT312+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n002.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 14:25:08 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 6.25/6.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.25/6.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.25/6.21  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.24/12.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.24/12.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.24/12.35  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.13/18.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.13/18.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.13/18.46  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 24.30/24.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.30/24.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.30/24.98  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 28.39/29.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.39/29.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.39/29.17  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 34.31/35.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.31/35.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.31/35.10  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.86/40.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.86/40.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.86/40.88  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.64/47.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.64/47.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.64/47.45  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.67/53.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.67/53.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.67/53.79  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.55/58.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.55/58.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.55/58.07  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.55/64.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.55/64.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.55/64.12  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 67.44/70.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.44/70.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.44/70.33  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 73.37/76.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.37/76.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.37/76.59  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.54/101.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 98.54/101.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 98.54/101.29  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.66/102.07  Timeout
%------------------------------------------------------------------------------