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

View Problem - Process Solution

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

% Computer : n028.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:18 EDT 2023

% Result   : Unknown 122.16s 124.77s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : ALG226+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n028.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 23:28:09 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 7.91/7.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.91/7.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.91/7.80  Peak sizes were: global stack 127648 kbytes, trail stack 4192 kbytes
% 15.49/15.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.49/15.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.49/15.93  Peak sizes were: global stack 127648 kbytes, trail stack 4192 kbytes
% 22.99/24.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.99/24.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.99/24.16  Peak sizes were: global stack 127520 kbytes, trail stack 4192 kbytes
% 31.14/32.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.14/32.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.14/32.97  Peak sizes were: global stack 127520 kbytes, trail stack 4192 kbytes
% 35.84/37.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.84/37.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.84/37.99  Peak sizes were: global stack 127648 kbytes, trail stack 4192 kbytes
% 43.24/45.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.24/45.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.24/45.77  Peak sizes were: global stack 127648 kbytes, trail stack 4192 kbytes
% 50.74/53.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.74/53.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.74/53.04  Peak sizes were: global stack 127648 kbytes, trail stack 4192 kbytes
% 58.37/60.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.37/60.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.37/60.49  Peak sizes were: global stack 127648 kbytes, trail stack 4192 kbytes
% 65.77/68.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.77/68.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.77/68.58  Peak sizes were: global stack 127648 kbytes, trail stack 4192 kbytes
% 70.81/73.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.81/73.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.81/73.43  Peak sizes were: global stack 127648 kbytes, trail stack 4192 kbytes
% 79.65/82.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.65/82.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.65/82.30  Peak sizes were: global stack 127648 kbytes, trail stack 4192 kbytes
% 122.11/124.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 122.11/124.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 122.11/124.07  Peak sizes were: global stack 127520 kbytes, trail stack 4192 kbytes
% 122.16/124.77  Timeout
%------------------------------------------------------------------------------