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

View Problem - Process Solution

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

% Computer : n027.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:24 EDT 2023

% Result   : Unknown 135.57s 134.13s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : CSR081+7 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.03/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n027.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % 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 01:08:50 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 9.76/9.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.76/9.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.76/9.62  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.53/19.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.53/19.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.53/19.02  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 29.09/29.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.09/29.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.09/29.24  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 38.70/38.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.70/38.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.70/38.67  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 42.17/42.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.17/42.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.17/42.05  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 52.07/52.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.07/52.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.07/52.30  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 61.49/62.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.49/62.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.49/62.26  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 71.12/71.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 71.12/71.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 71.12/71.80  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 80.81/81.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 80.81/81.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 80.81/81.18  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 83.91/84.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.91/84.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.91/84.19  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 93.53/93.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 93.53/93.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.53/93.55  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.53/133.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 135.53/133.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 135.53/133.99  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 135.57/134.13  Timeout
%------------------------------------------------------------------------------