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

View Problem - Process Solution

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

% Computer : n022.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 50.51s 62.72s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : PLA040+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.03/0.13  % Command  : leancop_casc.sh %s %d
% 0.13/0.34  % Computer : n022.cluster.edu
% 0.13/0.34  % Model    : x86_64 x86_64
% 0.13/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34  % Memory   : 8042.1875MB
% 0.13/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34  % CPULimit : 300
% 0.13/0.34  % WCLimit  : 600
% 0.13/0.34  % DateTime : Tue May 31 20:40:37 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 1.85/1.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.85/1.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.85/1.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.55/4.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.55/4.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.55/4.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.22/6.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.22/6.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.22/6.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.88/8.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.88/8.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.88/8.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.52/10.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.52/10.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.52/10.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.17/12.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.17/12.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.17/12.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.82/14.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.82/14.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.82/14.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.44/16.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.44/16.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.44/16.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.03/18.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.03/18.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.03/18.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.65/20.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.65/20.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.65/20.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.30/22.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.30/22.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.30/22.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.96/24.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.96/24.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.96/24.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.59/26.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.59/26.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.59/26.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.12/28.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.12/28.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.12/28.86  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.72/30.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.72/30.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.72/30.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.26/33.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.26/33.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.26/33.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.87/35.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.87/35.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.87/35.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.34/37.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.34/37.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.34/37.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.86/39.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.86/39.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.86/39.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.44/41.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.44/41.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.44/41.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.02/43.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.02/43.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.02/43.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.58/45.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.58/45.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.58/45.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.18/47.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.18/47.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.18/47.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.89/49.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.89/49.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.89/49.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.46/51.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.46/51.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.46/51.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.12/53.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.12/53.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.12/53.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.75/55.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.75/55.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.75/55.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.93/58.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.93/58.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.93/58.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.71/60.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.71/60.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.71/60.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.40/62.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.40/62.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.40/62.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------