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

View Problem - Process Solution

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

% Computer : n021.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 49.79s 62.66s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : PLA037+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.11/0.13  % Command  : leancop_casc.sh %s %d
% 0.12/0.34  % Computer : n021.cluster.edu
% 0.12/0.34  % Model    : x86_64 x86_64
% 0.12/0.34  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.34  % Memory   : 8042.1875MB
% 0.12/0.34  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.34  % CPULimit : 300
% 0.12/0.34  % WCLimit  : 600
% 0.12/0.34  % DateTime : Tue May 31 22:52:30 EDT 2022
% 0.12/0.34  % CPUTime  : 
% 1.76/1.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.76/1.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.76/1.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.46/4.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.46/4.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.46/4.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.16/6.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.16/6.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.16/6.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.85/8.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.85/8.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.85/8.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.51/10.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.51/10.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.51/10.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.19/12.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.19/12.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.19/12.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.79/14.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.79/14.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.79/14.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.50/16.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.50/16.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.50/16.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.16/18.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.16/18.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.16/18.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.79/20.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.79/20.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.79/20.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.43/22.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.43/22.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.43/22.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.10/24.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.10/24.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.10/24.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.81/26.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.81/26.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.81/26.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.65/29.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.65/29.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.65/29.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.43/31.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.43/31.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.43/31.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.02/33.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.02/33.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.02/33.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.71/35.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.71/35.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.71/35.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.31/37.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.31/37.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.31/37.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.80/39.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.80/39.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.80/39.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.44/41.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.44/41.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.44/41.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.19/43.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.19/43.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.19/43.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.77/45.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.77/45.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.77/45.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.46/47.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.46/47.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.46/47.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.02/49.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.02/49.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.02/49.62  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.69/51.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.69/51.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.69/51.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.24/53.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.24/53.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.24/53.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.87/55.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.87/55.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.87/55.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.50/57.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.50/57.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.50/57.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.14/60.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.14/60.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.14/60.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.66/62.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.66/62.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.66/62.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------