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

View Problem - Process Solution

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

% Computer : n028.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 90.81s 92.74s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : LAT286+4 : TPTP v8.1.2. Released v3.4.0.
% 0.13/0.13  % Command  : nanocop.sh %s %d
% 0.14/0.34  % Computer : n028.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 14:47:07 EDT 2023
% 0.14/0.34  % CPUTime  : 
% 5.50/5.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.50/5.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.50/5.55  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 10.87/11.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.87/11.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.87/11.67  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 16.14/16.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.14/16.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.14/16.82  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 21.37/22.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.37/22.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.37/22.02  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 25.07/25.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.07/25.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.07/25.62  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 30.26/31.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.26/31.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.26/31.33  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 35.43/36.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.43/36.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.43/36.43  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 40.80/41.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.80/41.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.80/41.77  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 46.05/46.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.05/46.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.05/46.91  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 49.64/50.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.64/50.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.64/50.51  Peak sizes were: global stack 127136 kbytes, trail stack 4192 kbytes
% 55.16/56.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.16/56.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.16/56.44  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 60.38/62.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.38/62.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.38/62.46  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 65.73/67.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.73/67.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.73/67.72  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 90.79/91.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 90.79/91.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 90.79/91.78  Peak sizes were: global stack 127008 kbytes, trail stack 4192 kbytes
% 90.81/92.74  Timeout
%------------------------------------------------------------------------------