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

View Problem - Process Solution

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

% Computer : n015.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 121.87s 124.97s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CAT033+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n015.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:26:43 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 8.22/8.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.22/8.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.22/8.11  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 16.24/16.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.24/16.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.24/16.34  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 24.26/24.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.26/24.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.26/24.65  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 32.19/32.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.19/32.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.19/32.82  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 37.22/38.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.22/38.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.22/38.37  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 45.10/46.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.10/46.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.10/46.38  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 52.86/54.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.86/54.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.86/54.38  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 60.46/62.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.46/62.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.46/62.69  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 68.30/71.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.30/71.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.30/71.13  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 73.44/76.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.44/76.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.44/76.86  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 81.31/84.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.31/84.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.31/84.68  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 121.85/124.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 121.85/124.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 121.85/124.30  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 121.87/124.97  Timeout
%------------------------------------------------------------------------------