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

View Problem - Process Solution

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

% Computer : n010.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:49 EDT 2023

% Result   : Unknown 83.56s 89.60s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12  % Problem  : CAT026+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n010.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:04:31 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 4.93/4.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.93/4.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.93/4.97  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 9.64/10.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.64/10.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.64/10.01  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 14.36/15.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.36/15.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.36/15.26  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 19.21/20.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.21/20.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.21/20.53  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 22.58/24.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.58/24.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.58/24.31  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 27.33/29.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.33/29.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.33/29.78  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 32.12/35.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.12/35.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.12/35.02  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 36.76/40.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.76/40.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.76/40.04  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 41.30/45.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.30/45.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.30/45.18  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 44.76/49.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.76/49.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.76/49.26  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 49.52/54.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.52/54.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.52/54.68  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 54.33/59.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.33/59.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.33/59.89  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 59.17/65.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.17/65.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.17/65.13  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 83.51/89.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.51/89.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.51/89.05  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 83.56/89.60  Timeout
%------------------------------------------------------------------------------