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

View Problem - Process Solution

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

% Computer : n017.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:39 EDT 2023

% Result   : Unknown 100.66s 104.96s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.13  % Problem  : LAT284+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.14/0.34  % Computer : n017.cluster.edu
% 0.14/0.34  % Model    : x86_64 x86_64
% 0.14/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.34  % Memory   : 8042.1875MB
% 0.14/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.34  % CPULimit : 300
% 0.14/0.34  % WCLimit  : 300
% 0.14/0.34  % DateTime : Thu May 18 13:33:19 EDT 2023
% 0.14/0.35  % CPUTime  : 
% 5.25/5.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.25/5.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.25/5.28  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 10.24/10.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.24/10.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.24/10.36  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 16.82/17.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.82/17.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.82/17.06  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 24.24/25.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.24/25.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.24/25.13  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 28.76/30.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.76/30.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.76/30.44  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 34.99/37.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.99/37.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.99/37.36  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 41.17/43.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.17/43.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.17/43.56  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 47.32/49.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.32/49.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.32/49.65  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 54.23/56.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.23/56.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.23/56.61  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 58.61/61.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.61/61.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.61/61.56  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 64.81/68.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.81/68.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.81/68.38  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 70.70/74.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.70/74.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.70/74.29  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 75.72/79.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 75.72/79.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 75.72/79.73  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 100.65/103.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 100.65/103.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 100.65/103.96  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 100.66/104.96  Timeout
%------------------------------------------------------------------------------