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

View Problem - Process Solution

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

% Computer : n027.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:54 EDT 2022

% Result   : Unknown 66.09s 78.27s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.00/0.12  % Problem  : HWV069+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.13/0.13  % Command  : leancop_casc.sh %s %d
% 0.13/0.34  % Computer : n027.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 : Fri Jun 17 00:04:51 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 2.26/2.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.26/2.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.26/2.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.75/5.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.75/5.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.75/5.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.10/8.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.10/8.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.10/8.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.26/11.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.26/11.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.26/11.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.62/15.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.62/15.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.62/15.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.67/18.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.67/18.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.67/18.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.94/20.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.94/20.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.94/20.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.28/23.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.28/23.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.28/23.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.86/28.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.86/28.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.86/28.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.42/31.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.42/31.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.42/31.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.90/34.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.90/34.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.90/34.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.02/37.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.02/37.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.02/37.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.30/40.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.30/40.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.30/40.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.47/44.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.47/44.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.47/44.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.82/47.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.82/47.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.82/47.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.84/50.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.84/50.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.84/50.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.82/52.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.82/52.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.82/52.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.61/53.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.61/53.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.61/53.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.74/56.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.74/56.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.74/56.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.71/58.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.71/58.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.71/58.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.84/60.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.84/60.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.84/60.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.94/62.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.94/62.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.94/62.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 52.94/64.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.94/64.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.94/64.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 55.03/66.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.03/66.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.03/66.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 57.12/68.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.12/68.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.12/68.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 66.00/77.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 66.00/77.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 66.00/77.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------