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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : PLA041+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:48 EDT 2022

% Result   : Unknown 51.10s 62.54s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.06/0.12  % Problem  : PLA041+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.06/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 22:24:41 EDT 2022
% 0.12/0.34  % CPUTime  : 
% 1.79/1.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.79/1.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.79/1.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.45/4.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.45/4.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.45/4.07  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.85/8.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.85/8.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.85/8.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.52/10.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.52/10.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.52/10.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.13/12.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.13/12.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.13/12.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.74/14.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.74/14.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.74/14.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.29/16.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.29/16.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.29/16.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.95/18.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.95/18.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.95/18.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.62/20.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.62/20.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.62/20.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.51/22.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.51/22.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.51/22.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.12/24.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.12/24.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.12/24.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.84/26.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.84/26.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.84/26.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.42/28.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.42/28.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.42/28.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.01/30.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.01/30.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.01/30.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.60/32.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.60/32.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.60/32.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.31/35.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.31/35.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.31/35.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.03/37.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.03/37.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.03/37.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.64/39.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.64/39.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.64/39.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.20/41.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.20/41.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.20/41.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.99/43.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.99/43.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.99/43.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.72/45.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.72/45.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.72/45.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.58/47.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.58/47.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.58/47.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.40/49.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.40/49.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.40/49.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.16/51.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.16/51.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.16/51.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.84/53.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.84/53.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.84/53.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.56/55.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.56/55.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.56/55.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.43/58.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.43/58.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.43/58.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.19/60.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.19/60.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.19/60.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 51.01/62.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.01/62.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.01/62.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------