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

View Problem - Process Solution

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

% Computer : n010.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 10:12:50 EDT 2023

% Result   : Unknown 82.38s 88.52s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : CAT029+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n010.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 20:07:46 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 4.92/4.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.92/4.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.92/4.94  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 9.59/10.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.59/10.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.59/10.02  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 14.33/15.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.33/15.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.33/15.22  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 18.96/20.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.96/20.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.96/20.40  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 22.26/24.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.26/24.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.26/24.25  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 27.00/29.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.00/29.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.00/29.71  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 31.62/34.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.62/34.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.62/34.88  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 36.22/39.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.22/39.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.22/39.99  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 40.83/45.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.83/45.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.83/45.16  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 44.02/49.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.02/49.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.02/49.03  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 48.74/53.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.74/53.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.74/53.59  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 53.49/58.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.49/58.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.49/58.85  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 58.17/63.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.17/63.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.17/63.95  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 82.35/87.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 82.35/87.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 82.35/87.76  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 82.38/88.52  Timeout
%------------------------------------------------------------------------------