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

View Problem - Process Solution

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

% Computer : n007.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:39 EDT 2023

% Result   : Unknown 135.61s 135.25s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR104+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n007.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Fri May 19 00:07:23 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 9.70/9.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.70/9.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.70/9.63  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.47/18.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.47/18.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.47/18.97  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 29.17/28.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.17/28.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.17/28.43  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 38.74/38.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.74/38.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.74/38.48  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 41.90/41.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.90/41.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.90/41.79  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 52.04/51.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.04/51.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.04/51.59  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 61.20/60.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.20/60.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.20/60.97  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 71.26/71.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.26/71.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.26/71.19  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 80.72/80.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.72/80.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.72/80.94  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 84.00/84.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 84.00/84.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 84.00/84.44  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 93.53/94.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 93.53/94.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.53/94.45  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.60/135.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 135.60/135.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 135.60/135.05  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.61/135.25  Timeout
%------------------------------------------------------------------------------