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

View Problem - Process Solution

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

% Computer : n008.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:52 EDT 2023

% Result   : Unknown 121.82s 124.79s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CAT036+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n008.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Thu May 18 20:16:00 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 8.18/8.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.18/8.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.18/8.11  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 16.09/16.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.09/16.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.09/16.22  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 23.91/24.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.91/24.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.91/24.39  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 31.88/32.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.88/32.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.88/32.89  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 36.92/38.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.92/38.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.92/38.35  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 44.72/46.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.72/46.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.72/46.14  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 52.60/54.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.60/54.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.60/54.55  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 60.62/63.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.62/63.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.62/63.04  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 68.69/71.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.69/71.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.69/71.30  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 73.75/76.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.75/76.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.75/76.66  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 81.61/84.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.61/84.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.61/84.63  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 121.72/123.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 121.72/123.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 121.72/123.87  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 121.82/124.79  Timeout
%------------------------------------------------------------------------------