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

View Problem - Process Solution

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

% Computer : n005.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 121.38s 124.82s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : ALG233+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n005.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:14:43 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 8.01/7.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.01/7.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.01/7.96  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 15.86/16.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.86/16.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.86/16.17  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 23.71/24.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.71/24.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.71/24.43  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 31.57/32.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.57/32.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.57/32.72  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 36.61/38.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.61/38.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.61/38.33  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 44.45/46.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.45/46.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.45/46.22  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 52.34/54.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.34/54.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.34/54.56  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 60.26/62.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.26/62.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.26/62.85  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 68.14/71.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.14/71.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.14/71.08  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 73.10/76.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 73.10/76.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 73.10/76.68  Peak sizes were: global stack 127768 kbytes, trail stack 4200 kbytes
% 81.13/84.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.13/84.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.13/84.69  Peak sizes were: global stack 127512 kbytes, trail stack 4200 kbytes
% 121.28/123.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 121.28/123.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 121.28/123.89  Peak sizes were: global stack 127640 kbytes, trail stack 4200 kbytes
% 121.38/124.81  Timeout
%------------------------------------------------------------------------------