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

View Problem - Process Solution

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

% Computer : n019.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:33 EDT 2023

% Result   : Unknown 136.78s 138.47s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CSR097+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n019.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:15:12 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 9.60/9.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.60/9.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.60/9.47  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.41/19.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.41/19.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.41/19.08  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 29.23/29.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.23/29.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.23/29.43  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 38.95/39.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.95/39.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.95/39.86  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 42.15/43.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.15/43.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.15/43.80  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 51.97/53.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.97/53.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.97/53.35  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 61.68/63.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.68/63.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.68/63.64  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 71.43/72.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.43/72.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.43/72.99  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 84.59/86.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 84.59/86.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 84.59/86.59  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 136.74/137.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 136.74/137.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 136.74/137.52  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 136.78/138.47  Timeout
%------------------------------------------------------------------------------