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

View Problem - Process Solution

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

% Computer : n006.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:20 EDT 2023

% Result   : Unknown 120.41s 124.70s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.11  % Problem  : ALG232+4 : TPTP v8.1.2. Released v3.4.0.
% 0.10/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n006.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:12:42 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 7.93/7.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.93/7.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.93/7.83  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 15.56/15.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.56/15.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.56/15.98  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 23.33/24.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.33/24.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.33/24.36  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 31.27/32.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.27/32.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.27/32.81  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 36.17/38.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.17/38.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.17/38.19  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 43.88/46.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.88/46.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.88/46.04  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 51.74/54.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.74/54.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.74/54.50  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 59.57/62.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.57/62.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.57/62.76  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 67.20/70.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.20/70.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.20/70.83  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 71.96/76.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.96/76.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.96/76.43  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 79.85/84.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.85/84.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.85/84.53  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 120.38/124.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 120.38/124.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 120.38/124.16  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 120.41/124.70  Timeout
%------------------------------------------------------------------------------