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

View Problem - Process Solution

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

% Computer : n021.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 128.57s 130.32s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.14  % Problem  : CAT037+4 : TPTP v8.1.2. Released v3.4.0.
% 0.08/0.14  % Command  : nanocop.sh %s %d
% 0.13/0.36  % Computer : n021.cluster.edu
% 0.13/0.36  % Model    : x86_64 x86_64
% 0.13/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.36  % Memory   : 8042.1875MB
% 0.13/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.36  % CPULimit : 300
% 0.13/0.36  % WCLimit  : 300
% 0.13/0.36  % DateTime : Thu May 18 20:14:33 EDT 2023
% 0.13/0.36  % CPUTime  : 
% 9.63/9.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.63/9.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.63/9.46  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 18.20/18.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.20/18.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.20/18.05  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 27.27/27.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.27/27.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.27/27.63  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 36.09/36.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.09/36.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.09/36.86  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 42.15/43.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.15/43.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.15/43.63  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 49.67/51.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.67/51.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.67/51.25  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 57.75/59.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.75/59.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.75/59.02  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 65.29/66.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.29/66.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.29/66.83  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 74.02/75.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 74.02/75.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.02/75.30  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 79.65/81.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.65/81.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.65/81.55  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 88.09/90.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 88.09/90.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 88.09/90.56  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 128.52/129.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 128.52/129.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 128.52/129.45  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 128.57/130.32  Timeout
%------------------------------------------------------------------------------