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

View Problem - Process Solution

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

% Computer : n025.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:08:19 EDT 2023

% Result   : Unknown 130.97s 133.13s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.11  % Problem  : ALG229+4 : TPTP v8.1.2. Released v3.4.0.
% 0.06/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n025.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 23:22:25 EDT 2023
% 0.13/0.33  % CPUTime  : 
% 9.49/9.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.49/9.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.49/9.40  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 18.30/18.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.30/18.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.30/18.06  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 29.22/29.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.22/29.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.22/29.49  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 37.98/38.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.98/38.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.98/38.75  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 43.35/44.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.35/44.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.35/44.86  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 52.19/53.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.19/53.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.19/53.35  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 61.36/63.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.36/63.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.36/63.05  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 69.05/70.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.05/70.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.05/70.95  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 77.09/79.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.09/79.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.09/79.61  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 82.35/85.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 82.35/85.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 82.35/85.19  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 90.27/93.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 90.27/93.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 90.27/93.04  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 130.93/132.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 130.93/132.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 130.93/132.66  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 130.97/133.13  Timeout
%------------------------------------------------------------------------------