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

View Problem - Process Solution

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

% Computer : n025.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 85.53s 86.39s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12  % Problem  : CAT032+4 : TPTP v8.1.2. Released v3.4.0.
% 0.04/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n025.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.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 20:28:22 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 4.66/4.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.66/4.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.66/4.70  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 8.92/9.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.92/9.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.92/9.66  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 13.81/15.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.81/15.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.81/15.28  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 18.12/20.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.12/20.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.12/20.09  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 21.20/23.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.20/23.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.20/23.95  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 25.88/28.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.88/28.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.88/28.64  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 30.32/33.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.32/33.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.32/33.59  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 34.58/38.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.58/38.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.58/38.67  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 38.91/42.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.91/42.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.91/42.91  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 42.07/46.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.07/46.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.07/46.80  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 46.31/51.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.31/51.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.31/51.15  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 50.85/56.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.85/56.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.85/56.38  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 55.22/61.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.22/61.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.22/61.54  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 85.49/85.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 85.49/85.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 85.49/85.56  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 85.53/86.38  Timeout
%------------------------------------------------------------------------------