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

View Problem - Process Solution

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

% Computer : n020.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 42.06s 62.63s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : HWV059+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.11/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.34  % Computer : n020.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 08:32:04 EDT 2022
% 0.12/0.34  % CPUTime  : 
% 1.56/1.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.56/1.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.56/1.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.05/3.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.05/3.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.05/3.80  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.35/5.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.35/5.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.35/5.82  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.81/7.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.81/7.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.81/7.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.13/9.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.13/9.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.13/9.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.57/12.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.57/12.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.57/12.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.01/14.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.01/14.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.01/14.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.35/16.14  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.35/16.14  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.35/16.14  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.76/18.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.76/18.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.76/18.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.10/20.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.10/20.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.10/20.38  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.56/22.41  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.56/22.41  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.56/22.41  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.84/24.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.84/24.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.84/24.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.37/26.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.37/26.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.37/26.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.72/28.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.72/28.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.72/28.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.18/30.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.18/30.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.18/30.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.50/32.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.50/32.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.50/32.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.85/34.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.85/34.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.85/34.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.44/37.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.44/37.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.44/37.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.92/39.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.92/39.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.92/39.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.38/41.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.38/41.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.38/41.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.72/43.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.72/43.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.72/43.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.07/45.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.07/45.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.07/45.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.51/47.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.51/47.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.51/47.38  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.70/49.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.70/49.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.70/49.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.20/51.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.20/51.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.20/51.49  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.52/53.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.52/53.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.52/53.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.99/55.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.99/55.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.99/55.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.33/57.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.33/57.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.33/57.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.62/59.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.62/59.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.62/59.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.97/61.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.97/61.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.97/61.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------