%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CSR105+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n027.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 11:04:39 EDT 2023

% Result   : Unknown 135.46s 135.19s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CSR105+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n027.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 : Fri May 19 00:55:50 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 9.56/9.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.56/9.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.56/9.48  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.31/19.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.31/19.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.31/19.04  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 29.21/29.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.21/29.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.21/29.41  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 39.18/40.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.18/40.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.18/40.05  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 42.27/43.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.27/43.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.27/43.74  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 51.72/52.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.72/52.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.72/52.95  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 61.11/62.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.11/62.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.11/62.20  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 70.28/71.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.28/71.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.28/71.42  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 83.50/84.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.50/84.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.50/84.46  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 135.39/135.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 135.39/135.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 135.39/135.14  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.46/135.19  Timeout
%------------------------------------------------------------------------------