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

View Problem - Process Solution

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

% Computer : n003.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 92.40s 98.87s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.13  % Problem  : CAT030+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.35  % Computer : n003.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:17:49 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 4.94/5.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.94/5.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.94/5.04  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 9.52/9.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.52/9.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.52/9.87  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 14.19/15.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.19/15.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.19/15.17  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 19.58/21.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.58/21.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.58/21.08  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 23.45/25.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.45/25.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.45/25.86  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 29.08/31.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.08/31.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.08/31.61  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 34.81/37.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.81/37.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.81/37.99  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 40.52/44.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.52/44.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.52/44.24  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 46.06/50.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.06/50.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.06/50.30  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 50.02/55.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.02/55.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.02/55.03  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 56.18/61.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.18/61.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.18/61.23  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 61.75/66.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.75/66.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.75/66.89  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 67.44/73.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.44/73.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.44/73.22  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 92.28/97.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 92.28/97.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 92.28/97.86  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 92.40/98.87  Timeout
%------------------------------------------------------------------------------