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

View Problem - Process Solution

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

% Computer : n014.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:39 EDT 2023

% Result   : Unknown 219.55s 215.04s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : SEU442+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n014.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 12:40:38 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 16.97/16.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.97/16.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.97/16.60  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 33.64/32.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.64/32.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.64/32.95  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 56.85/55.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.85/55.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.85/55.91  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 83.10/81.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.10/81.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.10/81.51  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 102.03/100.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 102.03/100.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 102.03/100.42  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 121.28/119.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 121.28/119.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 121.28/119.45  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 219.47/214.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 219.47/214.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 219.47/214.05  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 219.55/215.04  Timeout
%------------------------------------------------------------------------------