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

View Problem - Process Solution

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

% Computer : n012.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 128.26s 128.88s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.11  % Problem  : ALG227+4 : TPTP v8.1.2. Released v3.4.0.
% 0.10/0.12  % Command  : nanocop.sh %s %d
% 0.10/0.32  % Computer : n012.cluster.edu
% 0.10/0.32  % Model    : x86_64 x86_64
% 0.10/0.32  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.10/0.32  % Memory   : 8042.1875MB
% 0.10/0.32  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.10/0.32  % CPULimit : 300
% 0.10/0.32  % WCLimit  : 300
% 0.10/0.32  % DateTime : Thu May 18 23:31:07 EDT 2023
% 0.10/0.33  % CPUTime  : 
% 8.88/8.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.88/8.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.88/8.79  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 17.65/18.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.65/18.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.65/18.03  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 26.17/27.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.17/27.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.17/27.24  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 35.16/35.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.16/35.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.16/35.99  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 40.41/41.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.41/41.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.41/41.68  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 48.35/49.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.35/49.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.35/49.47  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 55.76/57.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.76/57.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.76/57.22  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 63.03/64.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 63.03/64.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 63.03/64.36  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 70.94/72.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.94/72.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.94/72.09  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 78.08/79.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.08/79.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.08/79.85  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 87.63/89.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 87.63/89.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 87.63/89.33  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 128.21/128.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 128.21/128.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 128.21/128.48  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 128.26/128.87  Timeout
%------------------------------------------------------------------------------