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

% Computer : n007.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:26 EDT 2023

% Result   : Unknown 193.28s 190.23s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.12  % Problem  : SEU406+4 : TPTP v8.1.2. Released v3.4.0.
% 0.12/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n007.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.19/0.33  % WCLimit  : 300
% 0.19/0.33  % DateTime : Thu May 18 13:18:32 EDT 2023
% 0.19/0.33  % CPUTime  : 
% 15.70/15.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.70/15.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.70/15.31  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 31.17/30.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.17/30.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.17/30.79  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 46.83/46.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.83/46.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.83/46.43  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 70.72/69.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.72/69.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.72/69.91  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 86.47/86.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 86.47/86.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 86.47/86.00  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 102.13/101.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 102.13/101.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 102.13/101.46  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 135.52/134.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 135.52/134.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 135.52/134.09  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 193.27/189.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 193.27/189.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 193.27/189.55  Peak sizes were: global stack 129176 kbytes, trail stack 4200 kbytes
% 193.28/190.23  Timeout
%------------------------------------------------------------------------------