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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : KRS285+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:10 EDT 2022

% Result   : Unknown 40.69s 62.72s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.13  % Problem  : KRS285+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.12/0.14  % Command  : leancop_casc.sh %s %d
% 0.13/0.35  % Computer : n029.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 600
% 0.13/0.35  % DateTime : Tue Jun  7 18:51:05 EDT 2022
% 0.13/0.35  % CPUTime  : 
% 1.49/1.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.49/1.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.49/1.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.06/3.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.06/3.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.06/3.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.47/5.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.47/5.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.47/5.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.92/7.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.92/7.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.92/7.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.30/9.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.30/9.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.30/9.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.61/12.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.61/12.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.61/12.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.02/14.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.02/14.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.02/14.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.38/16.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.38/16.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.38/16.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.70/18.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.70/18.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.70/18.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.10/20.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.10/20.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.10/20.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.40/22.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.40/22.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.40/22.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.74/24.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.74/24.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.74/24.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.05/26.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.05/26.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.05/26.52  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.39/28.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.39/28.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.39/28.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.72/30.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.72/30.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.72/30.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.09/32.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.09/32.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.09/32.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.40/34.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.40/34.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.40/34.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.65/36.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.65/36.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.65/36.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.75/38.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.75/38.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.75/38.86  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.19/41.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.19/41.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.19/41.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.45/43.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.45/43.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.45/43.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.81/45.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.81/45.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.81/45.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.05/47.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.05/47.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.05/47.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.54/49.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.54/49.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.54/49.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.81/51.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.81/51.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.81/51.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.12/53.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.12/53.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.12/53.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.52/55.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.52/55.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.52/55.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.81/57.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.81/57.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.81/57.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.21/59.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.21/59.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.21/59.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.61/61.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.61/61.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.61/61.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------