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

% Computer : n031.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 203.38s 199.24s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.11  % Problem  : SEU418+4 : TPTP v8.1.2. Released v3.4.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.32  % Computer : n031.cluster.edu
% 0.12/0.32  % Model    : x86_64 x86_64
% 0.12/0.32  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.32  % Memory   : 8042.1875MB
% 0.12/0.32  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.32  % CPULimit : 300
% 0.12/0.32  % WCLimit  : 300
% 0.12/0.32  % DateTime : Thu May 18 12:52:06 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 17.91/17.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.91/17.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.91/17.52  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 34.75/34.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.75/34.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.75/34.09  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 51.58/50.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.58/50.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.58/50.68  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 75.52/74.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 75.52/74.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 75.52/74.04  Peak sizes were: global stack 129944 kbytes, trail stack 4200 kbytes
% 92.60/91.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 92.60/91.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 92.60/91.33  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 109.61/107.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 109.61/107.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 109.61/107.77  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 143.72/140.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 143.72/140.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 143.72/140.81  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 203.35/198.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 203.35/198.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 203.35/198.41  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 203.38/199.24  Timeout
%------------------------------------------------------------------------------