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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : HWV075+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:56 EDT 2022

% Result   : Unknown 50.15s 62.67s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.13  % Problem  : HWV075+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.12/0.13  % Command  : leancop_casc.sh %s %d
% 0.13/0.35  % Computer : n004.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 600
% 0.13/0.35  % DateTime : Thu Jun 16 23:34:53 EDT 2022
% 0.13/0.35  % CPUTime  : 
% 1.75/1.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.75/1.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.75/1.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.33/3.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.33/3.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.33/3.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.02/6.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.02/6.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.02/6.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.64/8.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.64/8.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.64/8.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.18/10.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.18/10.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.18/10.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.85/12.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.85/12.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.85/12.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.45/14.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.45/14.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.45/14.38  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.17/16.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.17/16.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.17/16.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.75/18.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.75/18.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.75/18.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.36/20.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.36/20.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.36/20.55  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.32/22.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.32/22.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.32/22.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.18/25.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.18/25.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.18/25.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.99/26.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.99/26.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.99/26.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.76/29.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.76/29.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.76/29.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.45/31.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.45/31.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.45/31.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.08/33.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.08/33.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.08/33.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.84/35.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.84/35.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.84/35.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.31/37.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.31/37.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.31/37.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.52/38.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.52/38.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.52/38.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.28/41.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.28/41.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.28/41.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.85/43.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.85/43.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.85/43.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.45/45.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.45/45.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.45/45.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.18/47.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.18/47.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.18/47.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.88/49.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.88/49.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.88/49.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.52/51.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.52/51.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.52/51.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.27/53.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.27/53.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.27/53.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.90/55.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.90/55.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.90/55.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.61/57.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.61/57.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.61/57.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.32/60.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.32/60.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.32/60.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.98/62.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.98/62.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.98/62.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------