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

View Problem - Process Solution

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

% Computer : n018.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:24 EDT 2023

% Result   : Unknown 152.48s 153.94s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : CSR083+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.11/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n018.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:41:13 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 11.18/10.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.18/10.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.18/10.96  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 22.33/22.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.33/22.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.33/22.40  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 33.22/33.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.22/33.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.22/33.66  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 44.29/45.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.29/45.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.29/45.25  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 48.60/50.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.60/50.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.60/50.16  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 59.80/60.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.80/60.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.80/60.89  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 70.93/72.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.93/72.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.93/72.28  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 81.96/83.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.96/83.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.96/83.56  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 98.27/100.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 98.27/100.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 98.27/100.17  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 152.40/153.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 152.40/153.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 152.40/153.19  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 152.48/153.93  Timeout
%------------------------------------------------------------------------------