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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : LAT335+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:51 EDT 2023

% Result   : Unknown 98.15s 102.00s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : LAT335+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n027.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 14:20:10 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 6.04/6.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.04/6.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.04/6.06  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.96/12.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.96/12.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.96/12.19  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.91/18.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.91/18.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.91/18.50  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 23.78/24.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.78/24.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.78/24.63  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 27.76/29.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.76/29.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.76/29.02  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 33.62/35.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.62/35.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.62/35.00  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 39.62/41.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.62/41.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.62/41.37  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 45.54/47.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.54/47.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.54/47.49  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 51.48/53.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.48/53.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.48/53.81  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 55.49/58.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.49/58.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.49/58.03  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 61.23/63.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.23/63.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.23/63.90  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 67.17/70.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.17/70.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.17/70.36  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 73.00/76.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.00/76.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.00/76.42  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.13/101.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 98.13/101.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 98.13/101.19  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 98.15/102.00  Timeout
%------------------------------------------------------------------------------