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

View Problem - Process Solution

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

% Computer : n032.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:31 EDT 2023

% Result   : Unknown 209.85s 207.50s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.09  % Problem  : SEU421+4 : TPTP v8.1.2. Released v3.4.0.
% 0.08/0.09  % Command  : nanocop.sh %s %d
% 0.10/0.28  % Computer : n032.cluster.edu
% 0.10/0.28  % Model    : x86_64 x86_64
% 0.10/0.28  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.10/0.28  % Memory   : 8042.1875MB
% 0.10/0.28  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.10/0.28  % CPULimit : 300
% 0.10/0.28  % WCLimit  : 300
% 0.10/0.28  % DateTime : Thu May 18 13:40:45 EDT 2023
% 0.10/0.28  % CPUTime  : 
% 17.73/17.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.73/17.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.73/17.39  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 35.27/34.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.27/34.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.27/34.79  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 52.93/52.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.93/52.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.93/52.34  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 77.63/76.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.63/76.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.63/76.79  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 95.26/94.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 95.26/94.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 95.26/94.64  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 112.97/112.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 112.97/112.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 112.97/112.24  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 146.71/145.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 146.71/145.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 146.71/145.28  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 209.75/206.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 209.75/206.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 209.75/206.57  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 209.85/207.50  Timeout
%------------------------------------------------------------------------------