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

View Problem - Process Solution

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

% Computer : n005.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:23 EDT 2023

% Result   : Unknown 145.09s 146.53s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR080+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n005.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 300
% 0.12/0.34  % DateTime : Thu May 18 23:50:08 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 9.35/9.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.35/9.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.35/9.22  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.05/19.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.05/19.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.05/19.01  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 32.52/33.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.52/33.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.52/33.01  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 44.36/44.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.36/44.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.36/44.88  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 48.05/49.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.05/49.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.05/49.38  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 59.45/60.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.45/60.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.45/60.99  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 70.63/72.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.63/72.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.63/72.19  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 80.16/82.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.16/82.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.16/82.05  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 89.59/91.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 89.59/91.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 89.59/91.18  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 93.07/94.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 93.07/94.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.07/94.81  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 102.74/104.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 102.74/104.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 102.74/104.91  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 145.08/145.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 145.08/145.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 145.08/145.49  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 145.09/146.53  Timeout
%------------------------------------------------------------------------------