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

View Problem - Process Solution

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

% Computer : n024.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 35.58s 62.48s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : KRS289+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.03/0.12  % Command  : leancop_casc.sh %s %d
% 0.13/0.33  % Computer : n024.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 600
% 0.13/0.33  % DateTime : Tue Jun  7 12:10:34 EDT 2022
% 0.13/0.33  % CPUTime  : 
% 1.20/1.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.20/1.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.20/1.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.39/3.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.39/3.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.39/3.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.59/5.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.59/5.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.59/5.62  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.88/7.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.88/7.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.88/7.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.08/9.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.08/9.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.08/9.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.14/11.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.14/11.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.14/11.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.37/13.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.37/13.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.37/13.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.58/15.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.58/15.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.58/15.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.62/17.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.62/17.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.62/17.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.82/20.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.82/20.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.82/20.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.95/22.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.95/22.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.95/22.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.13/24.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.13/24.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.13/24.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.22/26.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.22/26.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.22/26.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.51/28.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.51/28.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.51/28.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.68/30.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.68/30.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.68/30.40  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.84/32.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.84/32.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.84/32.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.03/34.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.03/34.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.03/34.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.31/36.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.31/36.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.31/36.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.48/38.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.48/38.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.48/38.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.60/40.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.60/40.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.60/40.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.73/42.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.73/42.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.73/42.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.92/44.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.92/44.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.92/44.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.18/47.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.18/47.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.18/47.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.41/49.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.41/49.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.41/49.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.56/51.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.56/51.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.56/51.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.81/53.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.81/53.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.81/53.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.96/55.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.96/55.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.96/55.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.18/57.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.18/57.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.18/57.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.40/59.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.40/59.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.40/59.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.49/61.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.49/61.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.49/61.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------