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

View Problem - Process Solution

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

% Computer : n028.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 41.52s 62.55s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12  % Problem  : PLA042+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.03/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n028.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:00:36 EDT 2022
% 0.12/0.33  % CPUTime  : 
% 1.50/1.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.50/1.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.50/1.66  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 2.83/3.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.83/3.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.83/3.67  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 4.22/5.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.22/5.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.22/5.83  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 5.63/7.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.63/7.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.63/7.85  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 6.97/9.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.97/9.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.97/9.93  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 8.34/11.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.34/11.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.34/11.99  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 9.73/14.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.73/14.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.73/14.07  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 11.05/16.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.05/16.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.05/16.12  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 12.41/18.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.41/18.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.41/18.21  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 13.72/20.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.72/20.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.72/20.28  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 15.05/22.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.05/22.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.05/22.38  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 16.43/24.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.43/24.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.43/24.43  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 17.71/26.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.71/26.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.71/26.47  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 19.12/28.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.12/28.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.12/28.59  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 20.40/30.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.40/30.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.40/30.63  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 21.80/32.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.80/32.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.80/32.76  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 23.26/34.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.26/34.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.26/34.93  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 24.59/36.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.59/36.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.59/36.80  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 25.80/38.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.80/38.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.80/38.82  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 27.26/41.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.26/41.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.26/41.10  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 28.61/43.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.61/43.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.61/43.15  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 29.96/45.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.96/45.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.96/45.16  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 31.42/47.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.42/47.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.42/47.32  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 32.77/49.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.77/49.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.77/49.58  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 34.22/51.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.22/51.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.22/51.39  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 35.73/53.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.73/53.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.73/53.62  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 37.18/55.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.18/55.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.18/55.65  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 38.65/57.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.65/57.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.65/57.72  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 40.08/59.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.08/59.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.08/59.71  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
% 41.51/61.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.51/61.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.51/61.78  Peak sizes were: global stack 130976 kbytes, trail stack 4192 kbytes
%------------------------------------------------------------------------------