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

View Problem - Process Solution

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

% Computer : n015.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:21 EDT 2023

% Result   : Unknown 121.16s 124.79s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : ALG234+4 : TPTP v8.1.2. Released v3.4.0.
% 0.12/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n015.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:37:59 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 8.00/7.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.00/7.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.00/7.92  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 15.85/16.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.85/16.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.85/16.17  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 23.66/24.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.66/24.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.66/24.44  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 31.46/32.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.46/32.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.46/32.72  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 36.47/38.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.47/38.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.47/38.27  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 44.36/46.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.36/46.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.36/46.28  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 52.36/54.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.36/54.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.36/54.65  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 60.28/62.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.28/62.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.28/62.86  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 68.09/71.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.09/71.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.09/71.01  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 72.96/76.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.96/76.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.96/76.52  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 80.65/84.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.65/84.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.65/84.41  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 121.12/124.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 121.12/124.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 121.12/124.16  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 121.16/124.79  Timeout
%------------------------------------------------------------------------------