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

View Problem - Process Solution

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

% Result   : Unknown 55.67s 73.16s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.12  % Problem  : HWV082+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.12/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 06:19:52 EDT 2022
% 0.13/0.34  % CPUTime  : 
% 1.97/2.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.97/2.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.97/2.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.91/5.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.91/5.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.91/5.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.60/7.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.60/7.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.60/7.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.39/9.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.39/9.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.39/9.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.30/12.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.30/12.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.30/12.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.15/14.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.15/14.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.15/14.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.83/16.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.83/16.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.83/16.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.57/18.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.57/18.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.57/18.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.26/20.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.26/20.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.26/20.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.13/23.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.13/23.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.13/23.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.96/25.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.96/25.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.96/25.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.98/29.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.98/29.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.98/29.06  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.94/32.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.94/32.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.94/32.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.89/34.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.89/34.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.89/34.49  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.91/37.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.91/37.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.91/37.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.78/39.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.78/39.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.78/39.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.72/41.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.72/41.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.72/41.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.60/44.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.60/44.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.60/44.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.58/46.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.58/46.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.58/46.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.42/48.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.42/48.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.42/48.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.27/51.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.27/51.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.27/51.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.05/54.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.05/54.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.05/54.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.84/56.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.84/56.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.84/56.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.73/58.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.73/58.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.73/58.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.50/60.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.50/60.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.50/60.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.26/62.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.26/62.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.26/62.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.03/64.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.03/64.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.03/64.44  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 51.81/66.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.81/66.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.81/66.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 53.67/69.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 53.67/69.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 53.67/69.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 55.57/72.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.57/72.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.57/72.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------