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

View Problem - Process Solution

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

% Computer : n004.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 : Sat Jul 16 18:16:51 EDT 2022

% Result   : Unknown 61.48s 67.91s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.13  % Problem  : HWV062+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.04/0.14  % Command  : leancop_casc.sh %s %d
% 0.14/0.35  % Computer : n004.cluster.edu
% 0.14/0.35  % Model    : x86_64 x86_64
% 0.14/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35  % Memory   : 8042.1875MB
% 0.14/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35  % CPULimit : 300
% 0.14/0.35  % WCLimit  : 600
% 0.14/0.35  % DateTime : Thu Jun 16 22:51:53 EDT 2022
% 0.14/0.35  % CPUTime  : 
% 2.49/2.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.49/2.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.49/2.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.71/5.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.71/5.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.71/5.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.90/8.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.90/8.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.90/8.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.11/11.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.11/11.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.11/11.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.27/14.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.27/14.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.27/14.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.21/16.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.21/16.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.21/16.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.18/18.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.18/18.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.18/18.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.16/20.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.16/20.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.16/20.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.07/23.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.07/23.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.07/23.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.05/25.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.05/25.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.05/25.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.03/27.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.03/27.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.03/27.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.02/29.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.02/29.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.02/29.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.96/31.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.96/31.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.96/31.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.92/33.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.92/33.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.92/33.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.90/35.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.90/35.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.90/35.45  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.88/37.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.88/37.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.88/37.57  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.87/39.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.87/39.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.87/39.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.45/41.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.45/41.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.45/41.31  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.19/43.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.19/43.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.19/43.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.29/45.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.29/45.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.29/45.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.29/47.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.29/47.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.29/47.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.26/50.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.26/50.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.26/50.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.26/52.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.26/52.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.26/52.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.27/54.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.27/54.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.27/54.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.47/56.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.47/56.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.47/56.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 52.65/58.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.65/58.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.65/58.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 54.81/60.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.81/60.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.81/60.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 61.33/66.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.33/66.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.33/66.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------