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

View Problem - Process Solution

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

% Computer : n027.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 38.40s 62.54s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : KRS290+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.07/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n027.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:57:25 EDT 2022
% 0.12/0.34  % CPUTime  : 
% 1.44/1.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.44/1.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.44/1.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.84/3.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.84/3.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.84/3.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.07/5.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.07/5.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.07/5.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.43/7.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.43/7.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.43/7.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.61/9.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.61/9.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.61/9.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.92/11.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.92/11.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.92/11.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.12/13.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.12/13.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.12/13.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.38/16.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.38/16.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.38/16.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.66/18.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.66/18.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.66/18.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.82/20.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.82/20.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.82/20.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.05/22.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.05/22.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.05/22.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.31/24.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.31/24.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.31/24.31  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.59/26.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.59/26.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.59/26.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.86/28.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.86/28.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.86/28.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.13/30.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.13/30.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.13/30.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.40/32.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.40/32.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.40/32.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.64/34.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.64/34.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.64/34.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.94/36.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.94/36.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.94/36.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.11/38.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.11/38.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.11/38.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.50/41.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.50/41.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.50/41.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.78/42.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.78/42.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.78/42.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.05/45.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.05/45.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.05/45.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.40/47.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.40/47.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.40/47.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.65/49.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.65/49.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.65/49.22  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.07/51.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.07/51.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.07/51.40  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.43/53.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.43/53.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.43/53.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.66/55.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.66/55.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.66/55.40  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.88/57.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.88/57.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.88/57.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.17/59.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.17/59.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.17/59.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.36/61.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.36/61.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.36/61.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------