TSTP Solution File: KRS282+1 by leanCoP---2.2

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : KRS282+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% Transfm  : none
% Format   : tptp:raw
% Command  : leancop_casc.sh %s %d

% Computer : n029.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  : 600s
% DateTime : Sun Jul 17 03:14:09 EDT 2022

% Result   : Unknown 54.05s 63.03s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.14  % Problem  : KRS282+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.04/0.15  % Command  : leancop_casc.sh %s %d
% 0.14/0.37  % Computer : n029.cluster.edu
% 0.14/0.37  % Model    : x86_64 x86_64
% 0.14/0.37  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.37  % Memory   : 8042.1875MB
% 0.14/0.37  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.37  % CPULimit : 300
% 0.14/0.37  % WCLimit  : 600
% 0.14/0.37  % DateTime : Tue Jun  7 19:14:20 EDT 2022
% 0.14/0.37  % CPUTime  : 
% 1.91/2.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.91/2.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.91/2.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.66/4.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.66/4.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.66/4.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.50/6.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.50/6.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.50/6.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.21/8.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.21/8.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.21/8.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.10/10.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.10/10.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.10/10.57  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.86/12.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.86/12.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.86/12.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.59/14.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.59/14.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.59/14.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.44/16.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.44/16.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.44/16.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.27/18.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.27/18.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.27/18.80  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.07/20.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.07/20.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.07/20.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.89/22.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.89/22.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.89/22.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.70/25.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.70/25.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.70/25.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.55/27.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.55/27.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.55/27.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.32/29.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.32/29.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.32/29.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.10/31.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.10/31.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.10/31.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.95/33.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.95/33.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.95/33.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.76/35.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.76/35.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.76/35.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.44/37.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.44/37.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.44/37.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.27/39.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.27/39.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.27/39.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.06/41.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.06/41.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.06/41.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.82/43.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.82/43.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.82/43.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.64/45.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.64/45.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.64/45.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.35/47.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.35/47.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.35/47.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.20/50.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.20/50.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.20/50.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.90/52.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.90/52.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.90/52.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.74/54.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.74/54.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.74/54.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.59/56.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.59/56.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.59/56.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.44/58.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.44/58.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.44/58.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 52.16/60.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.16/60.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.16/60.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 53.93/62.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.93/62.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.93/62.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------