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

View Problem - Process Solution

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

% Computer : n023.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 38.15s 62.47s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.11  % Problem  : KRS288+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.06/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n023.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 09:18:38 EDT 2022
% 0.12/0.33  % CPUTime  : 
% 1.33/1.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.33/1.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.33/1.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.54/3.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.54/3.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.54/3.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.84/5.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.84/5.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.84/5.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.05/7.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.05/7.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.05/7.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.40/9.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.40/9.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.40/9.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.53/11.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.53/11.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.53/11.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.89/13.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.89/13.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.89/13.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.12/15.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.12/15.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.12/15.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.44/18.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.44/18.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.44/18.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.71/20.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.71/20.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.71/20.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.97/22.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.97/22.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.97/22.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.28/24.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.28/24.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.28/24.33  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.56/26.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.56/26.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.56/26.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.84/28.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.84/28.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.84/28.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.09/30.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.09/30.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.09/30.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.36/32.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.36/32.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.36/32.62  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.70/34.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.70/34.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.70/34.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.93/36.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.93/36.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.93/36.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.16/38.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.16/38.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.16/38.80  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.44/40.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.44/40.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.44/40.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.75/42.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.75/42.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.75/42.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.02/45.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.02/45.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.02/45.04  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.27/47.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.27/47.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.27/47.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.57/49.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.57/49.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.57/49.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.74/51.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.74/51.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.74/51.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.03/53.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.03/53.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.03/53.31  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.30/55.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.30/55.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.30/55.33  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.61/57.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.61/57.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.61/57.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.87/59.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.87/59.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.87/59.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.10/61.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.10/61.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.10/61.52  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------