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

View Problem - Process Solution

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

% Computer : n008.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:40 EDT 2023

% Result   : Unknown 89.04s 89.41s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : LAT289+4 : TPTP v8.1.2. Released v3.4.0.
% 0.12/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n008.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:02:58 EDT 2023
% 0.18/0.34  % CPUTime  : 
% 5.19/5.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.19/5.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.19/5.23  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 10.17/10.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.17/10.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.17/10.37  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 15.36/15.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.36/15.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.36/15.67  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 20.66/20.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.66/20.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.66/20.98  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 24.36/24.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.36/24.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.36/24.60  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 29.54/30.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.54/30.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.54/30.17  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 34.82/35.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.82/35.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.82/35.42  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 39.92/40.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.92/40.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.92/40.47  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 45.18/45.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.18/45.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.18/45.76  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 48.65/49.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.65/49.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.65/49.26  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 53.88/55.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.88/55.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.88/55.05  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 59.03/60.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.03/60.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.03/60.19  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 64.43/65.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.43/65.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.43/65.51  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 88.95/89.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 88.95/89.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 88.95/89.20  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 89.04/89.41  Timeout
%------------------------------------------------------------------------------