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

View Problem - Process Solution

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

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

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : HWV060+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.11/0.13  % Command  : leancop_casc.sh %s %d
% 0.13/0.34  % Computer : n004.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 : Thu Jun 16 21:33:24 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 1.76/1.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.76/1.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.76/1.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.46/4.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.46/4.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.46/4.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.10/6.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.10/6.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.10/6.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.92/8.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.92/8.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.92/8.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.60/10.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.60/10.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.60/10.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.16/12.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.16/12.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.16/12.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.64/14.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.64/14.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.64/14.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.15/16.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.15/16.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.15/16.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.69/18.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.69/18.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.69/18.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.21/20.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.21/20.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.21/20.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.63/22.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.63/22.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.63/22.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.14/24.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.14/24.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.14/24.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.76/26.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.76/26.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.76/26.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.29/28.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.29/28.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.29/28.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.85/30.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.85/30.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.85/30.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.36/33.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.36/33.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.36/33.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.85/35.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.85/35.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.85/35.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.41/37.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.41/37.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.41/37.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.97/39.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.97/39.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.97/39.31  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.65/41.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.65/41.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.65/41.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.25/43.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.25/43.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.25/43.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.83/45.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.83/45.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.83/45.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.43/47.62  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.43/47.62  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.43/47.62  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.94/49.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.94/49.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.94/49.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.52/51.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.52/51.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.52/51.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.15/54.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.15/54.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.15/54.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.77/56.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.77/56.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.77/56.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.50/58.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.50/58.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.50/58.22  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.08/60.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.08/60.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.08/60.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.73/62.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.73/62.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.73/62.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------