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

% Computer : n002.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:35 EDT 2023

% Result   : Unknown 207.39s 202.58s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : SEU429+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n002.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 13:10:15 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 17.80/17.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.80/17.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.80/17.33  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 35.48/35.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.48/35.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.48/35.00  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 53.11/52.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.11/52.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.11/52.49  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 77.90/77.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.90/77.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.90/77.03  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 95.76/94.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 95.76/94.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 95.76/94.27  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 113.57/111.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 113.57/111.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 113.57/111.76  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 147.92/145.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 147.92/145.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 147.92/145.32  Peak sizes were: global stack 129560 kbytes, trail stack 4200 kbytes
% 207.33/202.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 207.33/202.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 207.33/202.53  Peak sizes were: global stack 129432 kbytes, trail stack 4200 kbytes
% 207.39/202.58  Timeout
%------------------------------------------------------------------------------