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

View Problem - Process Solution

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

% Computer : n029.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:36 EDT 2023

% Result   : Unknown 207.32s 203.63s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : SEU433+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n029.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Thu May 18 13:29:37 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 17.93/17.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.93/17.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.93/17.48  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 35.70/35.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.70/35.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.70/35.06  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 53.46/52.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.46/52.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.46/52.64  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 78.18/77.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.18/77.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.18/77.08  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 95.85/95.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 95.85/95.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 95.85/95.07  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 113.06/112.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 113.06/112.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 113.06/112.24  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 147.38/145.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 147.38/145.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 147.38/145.37  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 207.30/202.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 207.30/202.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 207.30/202.91  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 207.32/203.62  Timeout
%------------------------------------------------------------------------------