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

View Problem - Process Solution

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

% Computer : n027.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:47 EDT 2022

% Result   : Unknown 49.65s 62.59s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : PLA034+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.11/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n027.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 600
% 0.12/0.33  % DateTime : Tue May 31 19:12:03 EDT 2022
% 0.12/0.33  % CPUTime  : 
% 1.78/1.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.78/1.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.78/1.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.45/4.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.45/4.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.45/4.04  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.11/6.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.11/6.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.11/6.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.76/8.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.76/8.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.76/8.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.41/10.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.41/10.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.41/10.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.03/12.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.03/12.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.03/12.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.69/14.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.69/14.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.69/14.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.32/16.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.32/16.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.32/16.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.99/18.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.99/18.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.99/18.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.58/20.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.58/20.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.58/20.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.28/22.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.28/22.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.28/22.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.93/24.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.93/24.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.93/24.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.56/26.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.56/26.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.56/26.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.16/28.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.16/28.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.16/28.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.86/30.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.86/30.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.86/30.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.49/33.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.49/33.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.49/33.04  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.15/35.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.15/35.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.15/35.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.74/37.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.74/37.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.74/37.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.44/39.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.44/39.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.44/39.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.15/41.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.15/41.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.15/41.38  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.88/43.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.88/43.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.88/43.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.47/45.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.47/45.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.47/45.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.18/47.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.18/47.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.18/47.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.79/49.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.79/49.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.79/49.57  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.41/51.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.41/51.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.41/51.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.97/53.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.97/53.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.97/53.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.63/55.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.63/55.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.63/55.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.24/57.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.24/57.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.24/57.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.91/59.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.91/59.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.91/59.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.59/62.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.59/62.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.59/62.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------