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

View Problem - Process Solution

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

% Computer : n032.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 41.18s 62.30s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.10  % Problem  : KRS284+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.06/0.10  % Command  : leancop_casc.sh %s %d
% 0.09/0.29  % Computer : n032.cluster.edu
% 0.09/0.29  % Model    : x86_64 x86_64
% 0.09/0.29  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.09/0.29  % Memory   : 8042.1875MB
% 0.09/0.29  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.09/0.29  % CPULimit : 300
% 0.09/0.29  % WCLimit  : 600
% 0.09/0.29  % DateTime : Tue Jun  7 08:46:50 EDT 2022
% 0.09/0.29  % CPUTime  : 
% 1.40/1.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.40/1.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.40/1.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.82/3.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.82/3.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.82/3.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.22/5.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.22/5.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.22/5.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.59/7.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.59/7.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.59/7.80  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.93/9.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.93/9.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.93/9.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.32/11.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.32/11.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.32/11.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.60/13.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.60/13.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.60/13.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.07/16.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.07/16.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.07/16.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.48/18.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.48/18.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.48/18.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.79/20.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.79/20.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.79/20.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.21/22.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.21/22.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.21/22.33  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.64/24.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.64/24.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.64/24.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.12/26.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.12/26.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.12/26.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.61/28.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.61/28.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.61/28.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.97/30.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.97/30.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.97/30.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.39/32.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.39/32.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.39/32.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.72/34.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.72/34.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.72/34.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.96/36.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.96/36.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.96/36.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.13/38.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.13/38.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.13/38.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.48/40.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.48/40.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.48/40.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.81/42.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.81/42.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.81/42.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.25/45.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.25/45.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.25/45.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.58/46.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.58/46.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.58/46.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.97/49.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.97/49.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.97/49.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.29/51.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.29/51.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.29/51.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.64/53.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.64/53.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.64/53.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.99/55.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.99/55.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.99/55.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.24/57.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.24/57.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.24/57.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.64/59.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.64/59.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.64/59.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.09/61.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.09/61.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.09/61.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------