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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CAT022+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:47 EDT 2023

% Result   : Unknown 100.23s 101.84s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CAT022+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n010.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Thu May 18 20:01:01 EDT 2023
% 0.13/0.33  % CPUTime  : 
% 5.18/5.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.18/5.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.18/5.22  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 10.68/10.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.68/10.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.68/10.78  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 16.42/17.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.42/17.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.42/17.24  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 21.35/22.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.35/22.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.35/22.71  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 25.26/26.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.26/26.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.26/26.97  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 31.05/32.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.05/32.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.05/32.83  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 38.08/40.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.08/40.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.08/40.41  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 43.75/46.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.75/46.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.75/46.11  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 49.27/52.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.27/52.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.27/52.18  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 53.52/57.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.52/57.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.52/57.26  Peak sizes were: global stack 126872 kbytes, trail stack 4200 kbytes
% 60.09/64.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.09/64.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.09/64.52  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 65.50/70.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.50/70.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.50/70.82  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 76.18/76.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.18/76.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.18/76.95  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 100.20/101.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 100.20/101.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 100.20/101.06  Peak sizes were: global stack 126744 kbytes, trail stack 4328 kbytes
% 100.23/101.84  Timeout
%------------------------------------------------------------------------------