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

View Problem - Process Solution

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

% Computer : n028.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:20 EDT 2023

% Result   : Unknown 155.55s 154.91s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : CSR076+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.11/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n028.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:07:03 EDT 2023
% 0.12/0.34  % CPUTime  : 
% 11.03/10.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.03/10.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.03/10.82  Peak sizes were: global stack 128160 kbytes, trail stack 4192 kbytes
% 22.08/22.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.08/22.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.08/22.37  Peak sizes were: global stack 128160 kbytes, trail stack 4192 kbytes
% 36.48/37.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.48/37.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.48/37.02  Peak sizes were: global stack 128160 kbytes, trail stack 4192 kbytes
% 49.33/50.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.33/50.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.33/50.07  Peak sizes were: global stack 128160 kbytes, trail stack 4192 kbytes
% 54.06/54.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.06/54.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.06/54.60  Peak sizes were: global stack 128288 kbytes, trail stack 4192 kbytes
% 66.80/67.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.80/67.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.80/67.56  Peak sizes were: global stack 128160 kbytes, trail stack 4192 kbytes
% 78.20/78.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 78.20/78.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 78.20/78.69  Peak sizes were: global stack 128160 kbytes, trail stack 4192 kbytes
% 88.59/89.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 88.59/89.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 88.59/89.07  Peak sizes were: global stack 128160 kbytes, trail stack 4192 kbytes
% 102.34/102.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 102.34/102.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 102.34/102.63  Peak sizes were: global stack 128288 kbytes, trail stack 4192 kbytes
% 155.40/153.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 155.40/153.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 155.40/153.88  Peak sizes were: global stack 128160 kbytes, trail stack 4192 kbytes
% 155.55/154.91  Timeout
%------------------------------------------------------------------------------