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

View Problem - Process Solution

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

% Computer : n019.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 122.97s 125.69s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : ALG225+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n019.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:32:33 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 8.07/7.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.07/7.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.07/7.99  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 16.16/16.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.16/16.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.16/16.37  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 24.01/24.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.01/24.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.01/24.49  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 31.97/32.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.97/32.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.97/32.82  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 37.05/38.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.05/38.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.05/38.42  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 44.99/46.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.99/46.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.99/46.32  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 52.97/54.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.97/54.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.97/54.61  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 60.70/62.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.70/62.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.70/62.72  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 68.40/70.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.40/70.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.40/70.94  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 73.65/76.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.65/76.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.65/76.96  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 81.66/84.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.66/84.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.66/84.70  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 122.95/125.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 122.95/125.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 122.95/125.17  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 122.97/125.69  Timeout
%------------------------------------------------------------------------------