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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : KRS287+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 42.36s 62.70s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12  % Problem  : KRS287+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.06/0.12  % Command  : leancop_casc.sh %s %d
% 0.13/0.33  % Computer : n020.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 13:59:36 EDT 2022
% 0.13/0.33  % CPUTime  : 
% 1.54/1.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.54/1.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.54/1.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.89/3.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.89/3.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.89/3.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.32/5.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.32/5.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.32/5.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.61/7.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.61/7.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.61/7.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.99/9.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.99/9.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.99/9.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.32/12.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.32/12.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.32/12.04  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.67/14.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.67/14.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.67/14.04  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.19/16.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.19/16.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.19/16.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.55/18.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.55/18.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.55/18.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.94/20.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.94/20.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.94/20.31  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.36/22.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.36/22.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.36/22.49  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.78/24.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.78/24.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.78/24.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.26/26.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.26/26.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.26/26.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.62/28.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.62/28.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.62/28.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.02/30.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.02/30.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.02/30.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.57/33.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.57/33.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.57/33.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.04/34.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.04/34.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.04/34.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.25/36.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.25/36.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.25/36.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.52/38.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.52/38.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.52/38.86  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.06/41.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.06/41.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.06/41.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.50/43.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.50/43.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.50/43.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.85/45.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.85/45.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.85/45.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.54/47.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.54/47.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.54/47.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.97/49.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.97/49.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.97/49.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.37/51.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.37/51.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.37/51.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.73/53.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.73/53.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.73/53.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.10/55.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.10/55.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.10/55.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.50/57.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.50/57.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.50/57.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.84/59.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.84/59.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.84/59.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.30/61.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.30/61.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.30/61.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------