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

View Problem - Process Solution

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

% Computer : n020.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 37.95s 60.46s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : KRS286+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.12/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n020.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 16:32:06 EDT 2022
% 0.12/0.33  % CPUTime  : 
% 1.49/1.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.49/1.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.49/1.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.82/3.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.82/3.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.82/3.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.19/5.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.19/5.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.19/5.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.51/7.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.51/7.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.51/7.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.81/9.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.81/9.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.81/9.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.12/12.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.12/12.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.12/12.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.31/13.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.31/13.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.31/13.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.75/16.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.75/16.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.75/16.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.99/18.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.99/18.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.99/18.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.32/20.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.32/20.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.32/20.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.69/22.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.69/22.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.69/22.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.95/24.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.95/24.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.95/24.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.22/26.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.22/26.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.22/26.45  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.45/28.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.45/28.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.45/28.45  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.72/30.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.72/30.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.72/30.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.05/32.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.05/32.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.05/32.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.27/34.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.27/34.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.27/34.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.38/36.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.38/36.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.38/36.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.32/37.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.32/37.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.32/37.52  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.47/38.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.47/38.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.47/38.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.63/40.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.63/40.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.63/40.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.91/43.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.91/43.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.91/43.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.15/45.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.15/45.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.15/45.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.42/47.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.42/47.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.42/47.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.61/49.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.61/49.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.61/49.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.87/51.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.87/51.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.87/51.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.09/53.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.09/53.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.09/53.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.31/55.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.31/55.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.31/55.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.64/57.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.64/57.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.64/57.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.89/59.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.89/59.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.89/59.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------