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

View Problem - Process Solution

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

% Computer : n032.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 103.33s 108.51s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.09  % Problem  : LAT306+4 : TPTP v8.1.2. Released v3.4.0.
% 0.00/0.09  % Command  : nanocop.sh %s %d
% 0.07/0.28  % Computer : n032.cluster.edu
% 0.07/0.28  % Model    : x86_64 x86_64
% 0.07/0.28  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.07/0.28  % Memory   : 8042.1875MB
% 0.07/0.28  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.07/0.28  % CPULimit : 300
% 0.07/0.28  % WCLimit  : 300
% 0.07/0.28  % DateTime : Thu May 18 14:04:23 EDT 2023
% 0.07/0.28  % CPUTime  : 
% 7.00/7.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.00/7.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.00/7.00  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 13.71/14.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.71/14.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.71/14.06  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 21.03/21.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.03/21.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.03/21.78  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.87/28.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.87/28.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.87/28.45  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 32.50/33.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.50/33.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.50/33.59  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 38.92/40.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.92/40.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.92/40.45  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 44.32/46.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.32/46.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.32/46.70  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 49.78/52.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.78/52.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.78/52.89  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.42/59.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.42/59.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.42/59.24  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 59.71/64.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.71/64.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.71/64.18  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 65.82/71.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.82/71.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.82/71.10  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.01/77.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.01/77.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.01/77.32  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 78.18/83.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.18/83.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.18/83.44  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 103.29/107.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 103.29/107.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 103.29/107.97  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 103.33/108.51  Timeout
%------------------------------------------------------------------------------