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

View Problem - Process Solution

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

% Computer : n023.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 54.62s 62.63s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : PLA035+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.11/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n023.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:37:41 EDT 2022
% 0.12/0.34  % CPUTime  : 
% 1.98/2.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.98/2.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.98/2.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.87/4.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.87/4.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.87/4.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.68/6.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.68/6.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.68/6.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.48/8.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.48/8.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.48/8.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.33/10.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.33/10.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.33/10.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.17/12.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.17/12.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.17/12.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.02/14.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.02/14.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.02/14.57  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.95/16.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.95/16.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.95/16.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.84/18.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.84/18.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.84/18.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.52/20.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.52/20.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.52/20.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.25/22.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.25/22.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.25/22.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.95/24.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.95/24.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.95/24.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.61/26.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.61/26.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.61/26.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.30/28.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.30/28.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.30/28.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.23/31.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.23/31.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.23/31.22  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.07/33.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.07/33.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.07/33.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.96/35.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.96/35.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.96/35.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.74/37.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.74/37.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.74/37.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.49/39.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.49/39.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.49/39.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.21/41.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.21/41.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.21/41.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.95/43.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.95/43.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.95/43.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.74/45.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.74/45.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.74/45.62  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.56/47.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.56/47.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.56/47.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.43/49.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.43/49.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.43/49.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.31/51.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.31/51.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.31/51.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.08/53.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.08/53.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.08/53.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.03/56.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.03/56.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.03/56.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.86/58.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.86/58.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.86/58.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 52.66/60.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.66/60.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.66/60.22  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 54.45/62.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.45/62.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.45/62.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------