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

View Problem - Process Solution

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

% Computer : n028.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:30 EDT 2023

% Result   : Unknown 215.42s 211.04s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : SEU419+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n028.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 12:54:30 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 18.66/18.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.66/18.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.66/18.16  Peak sizes were: global stack 129440 kbytes, trail stack 4192 kbytes
% 35.92/35.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.92/35.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.92/35.62  Peak sizes were: global stack 129440 kbytes, trail stack 4192 kbytes
% 53.90/53.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.90/53.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.90/53.80  Peak sizes were: global stack 129440 kbytes, trail stack 4192 kbytes
% 79.72/79.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.72/79.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.72/79.15  Peak sizes were: global stack 129568 kbytes, trail stack 4192 kbytes
% 99.39/98.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 99.39/98.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 99.39/98.01  Peak sizes were: global stack 129440 kbytes, trail stack 4192 kbytes
% 118.80/117.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 118.80/117.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 118.80/117.55  Peak sizes were: global stack 129440 kbytes, trail stack 4192 kbytes
% 215.38/210.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 215.38/210.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 215.38/210.36  Peak sizes were: global stack 129440 kbytes, trail stack 4192 kbytes
% 215.42/211.04  Timeout
%------------------------------------------------------------------------------