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

View Problem - Process Solution

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

% Computer : n009.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 155.83s 153.92s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.14  % Problem  : CSR085+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.08/0.14  % Command  : nanocop.sh %s %d
% 0.13/0.36  % Computer : n009.cluster.edu
% 0.13/0.36  % Model    : x86_64 x86_64
% 0.13/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.36  % Memory   : 8042.1875MB
% 0.13/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.36  % CPULimit : 300
% 0.13/0.36  % WCLimit  : 300
% 0.13/0.36  % DateTime : Thu May 18 23:52:47 EDT 2023
% 0.13/0.36  % CPUTime  : 
% 11.65/11.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.65/11.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.65/11.42  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 21.47/21.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.47/21.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.47/21.20  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 30.68/31.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.68/31.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.68/31.06  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 41.33/41.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.33/41.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.33/41.75  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 45.52/45.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.52/45.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.52/45.96  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 58.39/58.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 58.39/58.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.39/58.42  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 77.27/76.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 77.27/76.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 77.27/76.80  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 91.64/91.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 91.64/91.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 91.64/91.00  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 100.93/100.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 100.93/100.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 100.93/100.49  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 104.06/103.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 104.06/103.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 104.06/103.96  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 113.75/113.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 113.75/113.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 113.75/113.34  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 155.80/153.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 155.80/153.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 155.80/153.69  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 155.83/153.92  Timeout
%------------------------------------------------------------------------------