TSTP Solution File: CSR093+6 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CSR093+6 : TPTP v8.1.2. Bugfixed v7.3.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 11:04:31 EDT 2023

% Result   : Unknown 135.96s 132.59s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : CSR093+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n007.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 23:58:53 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 9.78/9.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.78/9.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.78/9.67  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.37/18.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.37/18.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.37/18.82  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 29.11/28.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.11/28.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.11/28.38  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 38.78/37.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.78/37.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.78/37.74  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 42.14/41.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.14/41.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.14/41.04  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 51.91/51.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.91/51.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.91/51.34  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 61.72/60.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.72/60.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.72/60.76  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 71.20/69.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.20/69.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.20/69.90  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 80.94/79.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.94/79.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.94/79.49  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 83.97/82.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.97/82.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.97/82.51  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 93.57/91.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 93.57/91.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.57/91.87  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.87/132.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 135.87/132.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 135.87/132.53  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.96/132.59  Timeout
%------------------------------------------------------------------------------