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

View Problem - Process Solution

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

% Computer : n013.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:04:37 EDT 2023

% Result   : Unknown 218.81s 213.07s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.13  % Problem  : SEU435+4 : TPTP v8.1.2. Released v3.4.0.
% 0.13/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.35  % Computer : n013.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 300
% 0.13/0.35  % DateTime : Thu May 18 12:58:47 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 18.25/17.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.25/17.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.25/17.74  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 36.32/35.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.32/35.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.32/35.35  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 54.40/53.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.40/53.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.40/53.02  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 78.83/76.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.83/76.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.83/76.77  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 100.00/97.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 100.00/97.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 100.00/97.54  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 120.88/118.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 120.88/118.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 120.88/118.00  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 155.34/151.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 155.34/151.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 155.34/151.75  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 218.75/212.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 218.75/212.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 218.75/212.79  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 218.81/213.07  Timeout
%------------------------------------------------------------------------------