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

View Problem - Process Solution

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

% Computer : n010.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:26 EDT 2023

% Result   : Unknown 147.83s 148.67s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CSR085+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n010.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 300
% 0.13/0.34  % DateTime : Fri May 19 00:35:27 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 11.06/10.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.06/10.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.06/10.85  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 22.03/22.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.03/22.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.03/22.30  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 33.26/33.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.26/33.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.26/33.92  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 44.37/45.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.37/45.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.37/45.16  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 48.57/50.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.57/50.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.57/50.05  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 59.11/60.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.11/60.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.11/60.30  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 69.64/70.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 69.64/70.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 69.64/70.55  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 80.57/81.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.57/81.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.57/81.39  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 94.63/95.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 94.63/95.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 94.63/95.75  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 147.69/147.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 147.69/147.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 147.69/147.71  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 147.83/148.67  Timeout
%------------------------------------------------------------------------------