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

View Problem - Process Solution

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

% Computer : n004.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:38 EDT 2023

% Result   : Unknown 223.81s 218.26s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.14  % Problem  : SEU437+4 : TPTP v8.1.2. Released v3.4.0.
% 0.08/0.14  % Command  : nanocop.sh %s %d
% 0.14/0.36  % Computer : n004.cluster.edu
% 0.14/0.36  % Model    : x86_64 x86_64
% 0.14/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.36  % Memory   : 8042.1875MB
% 0.14/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.36  % CPULimit : 300
% 0.14/0.36  % WCLimit  : 300
% 0.14/0.36  % DateTime : Thu May 18 12:44:03 EDT 2023
% 0.14/0.36  % CPUTime  : 
% 21.46/20.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.46/20.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.46/20.90  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 40.79/39.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.79/39.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.79/39.71  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 58.60/56.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.60/56.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.60/56.87  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 86.12/83.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 86.12/83.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 86.12/83.96  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 107.88/105.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 107.88/105.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 107.88/105.31  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 129.17/126.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 129.17/126.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 129.17/126.61  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 163.70/159.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 163.70/159.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 163.70/159.99  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 223.71/217.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 223.71/217.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 223.71/217.64  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 223.81/218.25  Timeout
%------------------------------------------------------------------------------