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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CAT034+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:51 EDT 2023

% Result   : Unknown 124.89s 123.83s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CAT034+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n025.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:24:40 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 8.58/8.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.58/8.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.58/8.46  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 16.99/16.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.99/16.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.99/16.78  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 25.49/25.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.49/25.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.49/25.07  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 33.94/33.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.94/33.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.94/33.38  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 39.12/38.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.12/38.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.12/38.55  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 47.43/46.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.43/46.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.43/46.74  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 55.57/54.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.57/54.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.57/54.85  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 63.93/63.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.93/63.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.93/63.34  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 71.92/71.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.92/71.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.92/71.36  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 77.01/76.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.01/76.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.01/76.78  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 85.07/84.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 85.07/84.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 85.07/84.82  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 124.87/123.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 124.87/123.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 124.87/123.64  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 124.89/123.83  Timeout
%------------------------------------------------------------------------------