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

View Problem - Process Solution

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

% Computer : n019.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 52.98s 62.67s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.13  % Problem  : PLA038+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.04/0.13  % Command  : leancop_casc.sh %s %d
% 0.13/0.35  % Computer : n019.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 600
% 0.13/0.35  % DateTime : Tue May 31 19:31:55 EDT 2022
% 0.13/0.35  % CPUTime  : 
% 1.95/2.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.95/2.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.95/2.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.78/4.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.78/4.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.78/4.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.58/6.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.58/6.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.58/6.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.47/8.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.47/8.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.47/8.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.21/10.33  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.21/10.33  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.21/10.33  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.96/12.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.96/12.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.96/12.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.72/14.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.72/14.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.72/14.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.45/16.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.45/16.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.45/16.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.23/18.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.23/18.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.23/18.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.94/20.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.94/20.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.94/20.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.67/22.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.67/22.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.67/22.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.50/24.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.50/24.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.50/24.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.28/27.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.28/27.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.28/27.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.13/29.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.13/29.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.13/29.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.83/31.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.83/31.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.83/31.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.67/33.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.67/33.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.67/33.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.31/35.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.31/35.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.31/35.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.10/37.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.10/37.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.10/37.40  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.76/39.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.76/39.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.76/39.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.48/41.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.48/41.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.48/41.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.21/43.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.21/43.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.21/43.62  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.03/45.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.03/45.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.03/45.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.87/47.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.87/47.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.87/47.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.65/49.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.65/49.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.65/49.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.33/51.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.33/51.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.33/51.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.05/53.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.05/53.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.05/53.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.71/55.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.71/55.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.71/55.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.44/58.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.44/58.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.44/58.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 51.15/60.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.15/60.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.15/60.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 52.86/62.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.86/62.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.86/62.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------