TSTP Solution File: CSR098+3 by nanoCoP---2.0

View Problem - Process Solution

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

% Computer : n011.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:34 EDT 2023

% Result   : Unknown 147.81s 149.86s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : CSR098+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.00/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n011.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:03:03 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 10.94/10.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.94/10.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.94/10.71  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 21.87/22.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.87/22.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.87/22.28  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 32.72/33.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.72/33.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.72/33.54  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 43.68/45.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.68/45.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.68/45.07  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 48.06/50.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.06/50.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.06/50.17  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 58.57/61.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.57/61.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.57/61.20  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 69.58/72.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.58/72.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.58/72.07  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 80.51/83.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.51/83.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.51/83.42  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 94.49/97.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.49/97.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.49/97.82  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 147.79/148.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 147.79/148.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 147.79/148.93  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 147.81/149.86  Timeout
%------------------------------------------------------------------------------