TSTP Solution File: KRS291+1 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : KRS291+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n013.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:26:37 EDT 2023

% Result   : Unknown 24.34s 41.76s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.11  % Problem  : KRS291+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.11/0.12  % Command  : nanocop.sh %s %d
% 0.11/0.33  % Computer : n013.cluster.edu
% 0.11/0.33  % Model    : x86_64 x86_64
% 0.11/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.33  % Memory   : 8042.1875MB
% 0.11/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.11/0.33  % CPULimit : 300
% 0.11/0.33  % WCLimit  : 300
% 0.11/0.33  % DateTime : Thu May 18 23:03:05 EDT 2023
% 0.11/0.33  % CPUTime  : 
% 1.25/1.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.25/1.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.25/1.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.51/3.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.51/3.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.51/3.52  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.70/5.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.70/5.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.70/5.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.89/7.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.89/7.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.89/7.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.96/9.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.96/9.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.96/9.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.25/11.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.25/11.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.25/11.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.45/13.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.45/13.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.45/13.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.66/15.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.66/15.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.66/15.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.83/18.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.83/18.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.83/18.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.11/20.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.11/20.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.11/20.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.43/22.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.43/22.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.43/22.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.62/24.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.62/24.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.62/24.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.83/26.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.83/26.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.83/26.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.96/28.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.96/28.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.96/28.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.40/30.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.40/30.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.40/30.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.64/32.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.64/32.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.64/32.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.69/34.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.69/34.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.69/34.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.98/36.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.98/36.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.98/36.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.14/38.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.14/38.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.14/38.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.30/40.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.30/40.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.30/40.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.34/41.76  Timeout
%------------------------------------------------------------------------------