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

View Problem - Process Solution

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

% Computer : n032.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:41 EDT 2023

% Result   : Unknown 96.20s 99.21s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.08  % Problem  : LAT292+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.08  % Command  : nanocop.sh %s %d
% 0.08/0.27  % Computer : n032.cluster.edu
% 0.08/0.27  % Model    : x86_64 x86_64
% 0.08/0.27  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.08/0.27  % Memory   : 8042.1875MB
% 0.08/0.27  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.08/0.27  % CPULimit : 300
% 0.08/0.27  % WCLimit  : 300
% 0.08/0.27  % DateTime : Thu May 18 14:08:53 EDT 2023
% 0.08/0.27  % CPUTime  : 
% 6.21/6.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.21/6.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.21/6.25  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 12.41/12.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.41/12.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.41/12.45  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 18.97/19.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.97/19.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.97/19.03  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 24.74/25.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.74/25.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.74/25.36  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 28.18/29.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.18/29.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.18/29.35  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 33.26/35.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.26/35.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.26/35.02  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 38.21/40.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.21/40.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.21/40.08  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 43.68/45.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.68/45.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.68/45.74  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 48.76/51.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.76/51.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.76/51.51  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 52.38/55.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.38/55.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.38/55.26  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 58.42/61.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.42/61.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.42/61.75  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 64.40/67.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.40/67.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.40/67.89  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 96.11/98.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 96.11/98.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 96.11/98.95  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 96.20/99.21  Timeout
%------------------------------------------------------------------------------