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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CSR110+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:42 EDT 2023

% Result   : Unknown 133.10s 131.15s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CSR110+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.12/0.34  % Computer : n018.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 : Fri May 19 00:40:28 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 9.24/9.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.24/9.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.24/9.12  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 18.83/18.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.83/18.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.83/18.87  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 27.85/27.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.85/27.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.85/27.68  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 36.94/37.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.94/37.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.94/37.06  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 39.83/40.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.83/40.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.83/40.46  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 49.35/49.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.35/49.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.35/49.91  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 59.02/59.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.02/59.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.02/59.39  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 68.62/68.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 68.62/68.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 68.62/68.71  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 78.19/78.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.19/78.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.19/78.00  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 81.38/81.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.38/81.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.38/81.16  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 91.08/90.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 91.08/90.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 91.08/90.59  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 133.05/130.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 133.05/130.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 133.05/130.91  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 133.10/131.15  Timeout
%------------------------------------------------------------------------------