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

View Problem - Process Solution

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

% Computer : n024.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 51.10s 62.61s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : KRS281+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.03/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n024.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  : 600
% 0.12/0.33  % DateTime : Tue Jun  7 12:28:34 EDT 2022
% 0.12/0.33  % CPUTime  : 
% 1.78/1.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.78/1.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.78/1.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.54/4.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.54/4.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.54/4.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.12/6.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.12/6.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.12/6.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.71/8.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.71/8.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.71/8.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.21/10.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.21/10.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.21/10.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.92/12.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.92/12.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.92/12.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.47/14.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.47/14.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.47/14.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.36/16.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.36/16.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.36/16.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.08/18.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.08/18.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.08/18.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.65/20.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.65/20.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.65/20.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.31/22.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.31/22.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.31/22.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.96/24.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.96/24.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.96/24.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.62/26.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.62/26.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.62/26.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.30/28.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.30/28.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.30/28.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.90/30.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.90/30.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.90/30.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.56/33.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.56/33.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.56/33.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.31/35.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.31/35.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.31/35.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.98/37.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.98/37.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.98/37.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.64/39.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.64/39.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.64/39.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.51/41.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.51/41.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.51/41.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.16/43.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.16/43.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.16/43.40  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.97/45.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.97/45.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.97/45.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.81/47.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.81/47.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.81/47.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.51/49.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.51/49.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.51/49.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.21/51.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.21/51.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.21/51.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.99/53.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.99/53.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.99/53.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.75/55.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.75/55.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.75/55.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.53/58.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.53/58.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.53/58.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.29/60.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.29/60.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.29/60.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 51.08/62.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.08/62.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.08/62.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------