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

View Problem - Process Solution

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

% Computer : n026.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:47 EDT 2023

% Result   : Unknown 84.17s 89.75s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.13  % Problem  : CAT021+4 : TPTP v8.1.2. Released v3.4.0.
% 0.08/0.14  % Command  : nanocop.sh %s %d
% 0.13/0.35  % Computer : n026.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 20:28:54 EDT 2023
% 0.13/0.36  % CPUTime  : 
% 5.02/5.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.02/5.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.02/5.02  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 9.77/10.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.77/10.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.77/10.14  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 14.65/15.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.65/15.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.65/15.43  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 19.47/20.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.47/20.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.47/20.54  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 22.93/24.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.93/24.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.93/24.42  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 27.77/29.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.77/29.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.77/29.93  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 32.40/34.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.40/34.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.40/34.97  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 37.34/40.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.34/40.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.34/40.37  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 42.17/45.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.17/45.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.17/45.53  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 45.47/49.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.47/49.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.47/49.25  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 50.31/54.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.31/54.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.31/54.90  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 55.24/60.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.24/60.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.24/60.12  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 59.88/65.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.88/65.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.88/65.00  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 84.09/89.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 84.09/89.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 84.09/89.05  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 84.17/89.75  Timeout
%------------------------------------------------------------------------------