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

View Problem - Process Solution

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

% Computer : n032.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:17 EDT 2023

% Result   : Unknown 119.83s 123.88s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.09  % Problem  : ALG224+4 : TPTP v8.1.2. Released v3.4.0.
% 0.03/0.09  % Command  : nanocop.sh %s %d
% 0.09/0.28  % Computer : n032.cluster.edu
% 0.09/0.28  % Model    : x86_64 x86_64
% 0.09/0.28  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.09/0.28  % Memory   : 8042.1875MB
% 0.09/0.28  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.09/0.28  % CPULimit : 300
% 0.09/0.28  % WCLimit  : 300
% 0.09/0.28  % DateTime : Thu May 18 23:32:11 EDT 2023
% 0.09/0.29  % CPUTime  : 
% 7.82/7.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.82/7.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.82/7.82  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 15.59/16.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.59/16.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.59/16.05  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 23.48/24.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.48/24.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.48/24.34  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 31.29/32.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.29/32.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.29/32.51  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 36.09/37.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.09/37.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.09/37.99  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 43.89/45.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.89/45.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.89/45.83  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 51.76/54.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.76/54.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.76/54.30  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 59.63/62.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.63/62.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.63/62.39  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 67.22/70.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 67.22/70.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 67.22/70.49  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 72.14/76.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.14/76.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.14/76.06  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 79.99/84.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.99/84.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.99/84.08  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 119.76/123.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 119.76/123.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 119.76/123.18  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 119.83/123.88  Timeout
%------------------------------------------------------------------------------