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

View Problem - Process Solution

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

% Computer : n011.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 12:03:34 EDT 2023

% Result   : Unknown 218.13s 213.06s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.11  % Problem  : SEU428+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.11/0.33  % Computer : n011.cluster.edu
% 0.11/0.33  % Model    : x86_64 x86_64
% 0.11/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.33  % Memory   : 8042.1875MB
% 0.11/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.11/0.33  % CPULimit : 300
% 0.11/0.33  % WCLimit  : 300
% 0.11/0.33  % DateTime : Thu May 18 13:37:00 EDT 2023
% 0.11/0.33  % CPUTime  : 
% 22.99/22.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.99/22.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.99/22.37  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 44.26/43.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.26/43.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.26/43.58  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 64.50/63.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 64.50/63.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 64.50/63.40  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 90.06/88.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 90.06/88.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 90.06/88.15  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 107.15/104.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 107.15/104.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 107.15/104.90  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 123.91/121.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 123.91/121.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 123.91/121.18  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 157.99/154.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 157.99/154.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 157.99/154.35  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 218.11/212.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 218.11/212.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 218.11/212.46  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 218.13/213.06  Timeout
%------------------------------------------------------------------------------