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

View Problem - Process Solution

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

% Computer : n029.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 : Mon Jul 18 17:25:48 EDT 2022

% Result   : Unknown 56.38s 62.43s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.11  % Problem  : PLA045+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.07/0.12  % Command  : leancop_casc.sh %s %d
% 0.11/0.33  % Computer : n029.cluster.edu
% 0.11/0.33  % Model    : x86_64 x86_64
% 0.11/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.11/0.33  % Memory   : 8042.1875MB
% 0.11/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.11/0.33  % CPULimit : 300
% 0.11/0.33  % WCLimit  : 600
% 0.11/0.33  % DateTime : Tue May 31 20:55:00 EDT 2022
% 0.11/0.33  % CPUTime  : 
% 2.12/2.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.12/2.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.12/2.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.07/4.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.07/4.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.07/4.33  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.04/6.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.04/6.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.04/6.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.95/8.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.95/8.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.95/8.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.80/10.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.80/10.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.80/10.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.70/12.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.70/12.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.70/12.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.54/14.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.54/14.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.54/14.57  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.47/16.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.47/16.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.47/16.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.36/18.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.36/18.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.36/18.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.20/20.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.20/20.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.20/20.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.11/22.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.11/22.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.11/22.86  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.93/24.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.93/24.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.93/24.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.91/26.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.91/26.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.91/26.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.75/29.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.75/29.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.75/29.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.65/31.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.65/31.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.65/31.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.51/33.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.51/33.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.51/33.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.51/35.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.51/35.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.51/35.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.26/37.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.26/37.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.26/37.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.10/39.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.10/39.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.10/39.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.07/41.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.07/41.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.07/41.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.22/43.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.22/43.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.22/43.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.10/45.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.10/45.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.10/45.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.84/47.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.84/47.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.84/47.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.53/49.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.53/49.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.53/49.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.27/51.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.27/51.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.27/51.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.12/53.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.12/53.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.12/53.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.87/55.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.87/55.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.87/55.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 52.57/57.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.57/57.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.57/57.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 54.35/59.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.35/59.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.35/59.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 56.34/62.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.34/62.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.34/62.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------