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

View Problem - Process Solution

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

% Computer : n021.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:11 EDT 2022

% Result   : Unknown 41.78s 62.60s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : KRS291+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.07/0.13  % Command  : leancop_casc.sh %s %d
% 0.13/0.34  % Computer : n021.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 600
% 0.13/0.34  % DateTime : Tue Jun  7 18:54:06 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 1.38/1.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.38/1.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.38/1.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.72/3.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.72/3.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.72/3.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.11/5.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.11/5.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.11/5.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.54/7.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.54/7.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.54/7.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.85/9.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.85/9.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.85/9.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.25/12.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.25/12.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.25/12.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.66/14.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.66/14.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.66/14.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.08/16.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.08/16.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.08/16.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.51/18.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.51/18.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.51/18.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.00/20.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.00/20.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.00/20.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.45/22.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.45/22.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.45/22.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.69/24.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.69/24.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.69/24.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.15/26.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.15/26.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.15/26.62  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.50/28.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.50/28.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.50/28.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.94/30.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.94/30.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.94/30.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.40/32.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.40/32.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.40/32.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.70/34.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.70/34.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.70/34.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.91/36.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.91/36.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.91/36.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.23/38.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.23/38.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.23/38.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.42/40.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.42/40.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.42/40.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.75/43.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.75/43.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.75/43.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.17/45.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.17/45.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.17/45.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.38/47.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.38/47.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.38/47.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.67/49.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.67/49.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.67/49.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.00/51.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.00/51.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.00/51.40  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.36/53.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.36/53.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.36/53.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.66/55.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.66/55.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.66/55.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.81/57.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.81/57.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.81/57.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.26/59.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.26/59.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.26/59.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.76/61.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.76/61.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.76/61.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------