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

View Problem - Process Solution

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

% Computer : n012.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:48 EDT 2023

% Result   : Unknown 81.54s 87.33s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.12  % Problem  : CAT025+4 : TPTP v8.1.2. Released v3.4.0.
% 0.12/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n012.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:12:51 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 5.30/5.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.30/5.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.30/5.37  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 10.57/10.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.57/10.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.57/10.58  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 15.05/14.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.05/14.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.05/14.99  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 19.40/20.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.40/20.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.40/20.09  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 22.58/24.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.58/24.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.58/24.08  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 26.94/28.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.94/28.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.94/28.32  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 31.36/33.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.36/33.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.36/33.49  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 35.70/38.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.70/38.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.70/38.66  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 40.18/43.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.18/43.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.18/43.95  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 43.17/47.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.17/47.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.17/47.76  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 47.58/52.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.58/52.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.58/52.13  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 52.01/57.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.01/57.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.01/57.38  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 56.34/62.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.34/62.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.34/62.42  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 81.47/86.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.47/86.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.47/86.67  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 81.54/87.33  Timeout
%------------------------------------------------------------------------------