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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : PLA043+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 48.82s 62.65s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : PLA043+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.07/0.13  % Command  : leancop_casc.sh %s %d
% 0.13/0.34  % Computer : n021.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 22:21:00 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 1.78/1.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.78/1.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.78/1.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.47/4.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.47/4.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.47/4.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.16/6.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.16/6.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.16/6.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.78/8.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.78/8.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.78/8.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.41/10.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.41/10.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.41/10.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.94/12.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.94/12.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.94/12.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.56/14.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.56/14.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.56/14.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.20/16.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.20/16.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.20/16.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.94/18.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.94/18.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.94/18.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.60/20.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.60/20.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.60/20.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.24/22.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.24/22.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.24/22.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.79/24.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.79/24.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.79/24.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.48/26.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.48/26.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.48/26.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.21/28.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.21/28.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.21/28.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.77/30.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.77/30.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.77/30.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.36/33.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.36/33.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.36/33.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.04/35.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.04/35.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.04/35.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.74/37.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.74/37.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.74/37.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.34/39.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.34/39.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.34/39.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.96/41.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.96/41.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.96/41.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.55/43.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.55/43.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.55/43.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.15/45.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.15/45.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.15/45.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.79/47.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.79/47.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.79/47.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.36/49.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.36/49.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.36/49.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.88/51.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.88/51.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.88/51.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.49/53.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.49/53.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.49/53.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.09/55.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.09/55.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.09/55.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.70/57.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.70/57.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.70/57.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.25/60.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.25/60.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.25/60.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.77/61.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.77/61.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.77/61.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------