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

View Problem - Process Solution

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

% Computer : n015.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:48 EDT 2022

% Result   : Unknown 44.20s 62.66s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : HWV056+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.12/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.34  % Computer : n015.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 : Fri Jun 17 06:31:42 EDT 2022
% 0.12/0.34  % CPUTime  : 
% 1.65/1.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.65/1.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.65/1.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.17/3.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.17/3.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.17/3.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.56/5.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.56/5.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.56/5.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.11/8.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.11/8.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.11/8.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.56/10.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.56/10.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.56/10.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.93/12.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.93/12.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.93/12.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.41/14.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.41/14.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.41/14.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.97/16.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.97/16.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.97/16.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.50/18.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.50/18.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.50/18.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.97/20.45  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.97/20.45  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.97/20.45  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.33/22.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.33/22.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.33/22.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.85/24.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.85/24.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.85/24.57  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.30/26.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.30/26.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.30/26.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.74/28.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.74/28.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.74/28.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.15/30.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.15/30.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.15/30.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.69/32.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.69/32.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.69/32.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.10/35.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.10/35.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.10/35.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.69/37.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.69/37.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.69/37.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.17/39.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.17/39.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.17/39.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.55/41.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.55/41.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.55/41.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.02/43.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.02/43.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.02/43.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.53/45.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.53/45.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.53/45.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.99/47.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.99/47.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.99/47.40  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.40/49.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.40/49.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.40/49.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.87/51.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.87/51.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.87/51.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.35/53.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.35/53.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.35/53.62  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.72/55.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.72/55.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.72/55.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.22/57.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.22/57.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.22/57.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.66/59.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.66/59.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.66/59.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.16/61.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.16/61.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.16/61.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------