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

View Problem - Process Solution

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

% Computer : n009.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 100.96s 105.33s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.13  % Problem  : LAT290+4 : TPTP v8.1.2. Released v3.4.0.
% 0.08/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.35  % Computer : n009.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 300
% 0.13/0.35  % DateTime : Thu May 18 14:31:52 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 5.67/5.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.67/5.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.67/5.66  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 11.45/12.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.45/12.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.45/12.14  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 17.53/18.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.53/18.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.53/18.63  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 23.18/24.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.18/24.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.18/24.42  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.97/28.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.97/28.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.97/28.93  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 32.66/34.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.66/34.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.66/34.90  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 38.58/41.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.58/41.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.58/41.33  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 45.40/48.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.40/48.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.40/48.44  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 52.14/55.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.14/55.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.14/55.65  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 56.53/60.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.53/60.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.53/60.66  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 63.67/68.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.67/68.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.67/68.52  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 69.99/75.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.99/75.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.99/75.02  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 76.21/81.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.21/81.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.21/81.17  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 100.89/105.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 100.89/105.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 100.89/105.07  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 100.96/105.33  Timeout
%------------------------------------------------------------------------------