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

View Problem - Process Solution

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

% Result   : Unknown 134.95s 134.26s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CSR076+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n007.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.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Fri May 19 00:29:08 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 9.74/9.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.74/9.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.74/9.63  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.45/18.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.45/18.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.45/18.98  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 29.12/28.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.12/28.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.12/28.33  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 38.71/37.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.71/37.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.71/37.54  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 42.06/40.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.06/40.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.06/40.91  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 51.41/50.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.41/50.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.41/50.78  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 60.69/60.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 60.69/60.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 60.69/60.10  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 70.03/69.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.03/69.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.03/69.45  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 79.71/79.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 79.71/79.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 79.71/79.17  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 83.06/82.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 83.06/82.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.06/82.37  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 92.66/92.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 92.66/92.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 92.66/92.57  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 134.88/133.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 134.88/133.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 134.88/133.22  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 134.95/134.26  Timeout
%------------------------------------------------------------------------------