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

View Problem - Process Solution

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

% Computer : n028.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:36 EDT 2023

% Result   : Unknown 134.12s 134.10s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : CSR101+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.12/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n028.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 23:59:18 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 9.65/9.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.65/9.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.65/9.51  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 19.16/18.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.16/18.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.16/18.83  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 28.88/28.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.88/28.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.88/28.32  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 38.22/38.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.22/38.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.22/38.35  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 41.11/41.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.11/41.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.11/41.42  Peak sizes were: global stack 128288 kbytes, trail stack 4192 kbytes
% 50.53/50.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.53/50.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.53/50.80  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 59.98/60.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.98/60.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.98/60.27  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 69.61/69.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.61/69.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.61/69.78  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 79.30/80.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.30/80.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.30/80.01  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 82.38/83.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 82.38/83.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 82.38/83.19  Peak sizes were: global stack 128288 kbytes, trail stack 4192 kbytes
% 91.76/92.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 91.76/92.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 91.76/92.21  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 134.05/133.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 134.05/133.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 134.05/133.17  Peak sizes were: global stack 128032 kbytes, trail stack 4192 kbytes
% 134.12/134.10  Timeout
%------------------------------------------------------------------------------