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

View Problem - Process Solution

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

% Computer : n027.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:41 EDT 2023

% Result   : Unknown 104.82s 107.06s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : LAT295+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n027.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:50:11 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 6.56/6.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.56/6.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.56/6.57  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 12.63/13.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.63/13.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.63/13.39  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 18.60/19.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.60/19.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.60/19.49  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 24.65/25.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.65/25.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.65/25.93  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 29.29/30.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.29/30.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.29/30.71  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 35.61/37.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.61/37.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.61/37.54  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 41.72/43.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.72/43.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.72/43.52  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 47.97/49.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.97/49.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.97/49.88  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.62/56.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.62/56.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.62/56.50  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 59.46/61.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.46/61.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.46/61.95  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 66.75/69.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.75/69.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.75/69.55  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 104.78/106.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 104.78/106.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 104.78/106.44  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 104.82/107.06  Timeout
%------------------------------------------------------------------------------