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

View Problem - Process Solution

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

% Computer : n016.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:57 EDT 2022

% Result   : Unknown 44.08s 62.85s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.14  % Problem  : HWV077+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.08/0.14  % Command  : leancop_casc.sh %s %d
% 0.14/0.36  % Computer : n016.cluster.edu
% 0.14/0.36  % Model    : x86_64 x86_64
% 0.14/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.36  % Memory   : 8042.1875MB
% 0.14/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.36  % CPULimit : 300
% 0.14/0.36  % WCLimit  : 600
% 0.14/0.36  % DateTime : Fri Jun 17 00:41:05 EDT 2022
% 0.14/0.36  % CPUTime  : 
% 1.64/1.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.64/1.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.64/1.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.10/3.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.10/3.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.10/3.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.56/5.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.56/5.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.56/5.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.97/8.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.97/8.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.97/8.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.38/10.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.38/10.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.38/10.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.02/12.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.02/12.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.02/12.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.47/14.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.47/14.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.47/14.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.95/16.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.95/16.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.95/16.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.38/18.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.38/18.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.38/18.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.87/20.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.87/20.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.87/20.49  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.33/22.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.33/22.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.33/22.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.75/24.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.75/24.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.75/24.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.24/26.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.24/26.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.24/26.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.67/28.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.67/28.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.67/28.80  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.08/30.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.08/30.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.08/30.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.57/32.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.57/32.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.57/32.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.00/35.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.00/35.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.00/35.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.53/37.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.53/37.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.53/37.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.97/39.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.97/39.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.97/39.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.39/41.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.39/41.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.39/41.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.87/43.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.87/43.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.87/43.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.27/45.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.27/45.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.27/45.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.75/47.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.75/47.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.75/47.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.24/49.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.24/49.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.24/49.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.70/51.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.70/51.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.70/51.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.14/53.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.14/53.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.14/53.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.61/55.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.61/55.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.61/55.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.09/58.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.09/58.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.09/58.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.55/60.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.55/60.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.55/60.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.06/62.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.06/62.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.06/62.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------