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

View Problem - Process Solution

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

% Computer : n007.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 91.17s 94.85s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12  % Problem  : LAT285+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n007.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Thu May 18 14:05:27 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 5.48/5.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.48/5.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.48/5.56  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.06/11.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.06/11.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.06/11.81  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 16.45/17.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.45/17.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.45/17.99  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 21.79/24.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.79/24.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.79/24.12  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 25.52/27.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.52/27.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.52/27.78  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 31.04/33.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.04/33.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.04/33.63  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 36.21/39.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.21/39.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.21/39.63  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 41.22/44.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.22/44.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.22/44.65  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 46.57/50.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.57/50.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.57/50.08  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 50.22/53.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.22/53.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.22/53.63  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 55.40/59.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.40/59.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.40/59.32  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 60.80/64.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.80/64.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.80/64.74  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 66.29/70.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.29/70.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.29/70.89  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 91.17/94.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 91.17/94.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 91.17/94.83  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 91.17/94.85  Timeout
%------------------------------------------------------------------------------