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

View Problem - Process Solution

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

% Computer : n020.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.64s 136.39s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR104+7 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.13  % Command  : nanocop.sh %s %d
% 0.14/0.34  % Computer : n020.cluster.edu
% 0.14/0.34  % Model    : x86_64 x86_64
% 0.14/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.34  % Memory   : 8042.1875MB
% 0.14/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.34  % CPULimit : 300
% 0.14/0.34  % WCLimit  : 300
% 0.14/0.34  % DateTime : Fri May 19 00:27:47 EDT 2023
% 0.14/0.34  % CPUTime  : 
% 9.78/9.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.78/9.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.78/9.64  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.37/18.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.37/18.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.37/18.91  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 28.60/27.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.60/27.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.60/27.91  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 38.45/37.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.45/37.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.45/37.74  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 41.70/41.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.70/41.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.70/41.92  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 51.45/52.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.45/52.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.45/52.27  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 61.26/62.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.26/62.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.26/62.61  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 70.95/71.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.95/71.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.95/71.99  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 80.64/82.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.64/82.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.64/82.24  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 83.73/85.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.73/85.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.73/85.36  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 93.34/94.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 93.34/94.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.34/94.69  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.54/135.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 135.54/135.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 135.54/135.35  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.64/136.39  Timeout
%------------------------------------------------------------------------------