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

View Problem - Process Solution

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

% Computer : n010.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:52 EDT 2023

% Result   : Unknown 97.68s 101.96s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : LAT336+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n010.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.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Thu May 18 14:25:47 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 5.75/5.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.75/5.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.75/5.74  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 11.35/11.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.35/11.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.35/11.96  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 17.00/18.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.00/18.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.00/18.13  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 22.49/24.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.49/24.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.49/24.29  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 26.42/28.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.42/28.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.42/28.98  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 32.40/35.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.40/35.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.40/35.09  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 38.49/41.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.49/41.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.49/41.31  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 44.44/47.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.44/47.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.44/47.49  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 50.34/53.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.34/53.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.34/53.68  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 54.39/58.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.39/58.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.39/58.13  Peak sizes were: global stack 127256 kbytes, trail stack 4200 kbytes
% 60.29/64.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.29/64.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.29/64.02  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 66.16/70.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.16/70.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.16/70.25  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 72.14/76.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.14/76.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.14/76.54  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.66/101.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 97.66/101.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 97.66/101.52  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 97.68/101.96  Timeout
%------------------------------------------------------------------------------