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

View Problem - Process Solution

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

% Computer : n022.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.27s 89.59s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CAT027+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n022.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Thu May 18 20:10:20 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 4.85/4.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.85/4.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.85/4.86  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 9.53/10.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.53/10.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.53/10.05  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 14.29/15.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.29/15.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.29/15.25  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 18.93/20.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.93/20.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.93/20.34  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 22.25/24.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.25/24.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.25/24.23  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 26.97/29.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.97/29.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.97/29.75  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 31.86/35.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.86/35.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.86/35.13  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 36.67/40.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.67/40.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.67/40.27  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 41.45/45.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.45/45.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.45/45.31  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 44.84/49.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.84/49.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.84/49.21  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 49.43/54.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.43/54.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.43/54.54  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 54.30/59.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.30/59.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.30/59.93  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 58.96/65.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.96/65.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.96/65.00  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 83.24/88.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.24/88.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.24/88.94  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 83.27/89.59  Timeout
%------------------------------------------------------------------------------