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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : leanCoP---2.2
% Problem  : HWV086+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:17:01 EDT 2022

% Result   : Unknown 51.72s 62.72s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.13  % Problem  : HWV086+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.04/0.14  % Command  : leancop_casc.sh %s %d
% 0.14/0.36  % Computer : n020.cluster.edu
% 0.14/0.36  % Model    : x86_64 x86_64
% 0.14/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.36  % Memory   : 8042.1875MB
% 0.14/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.36  % CPULimit : 300
% 0.14/0.36  % WCLimit  : 600
% 0.14/0.36  % DateTime : Fri Jun 17 08:40:04 EDT 2022
% 0.14/0.36  % CPUTime  : 
% 1.94/2.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.94/2.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.94/2.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.73/4.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.73/4.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.73/4.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.45/6.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.45/6.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.45/6.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.11/8.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.11/8.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.11/8.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.90/10.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.90/10.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.90/10.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.55/12.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.55/12.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.55/12.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.30/14.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.30/14.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.30/14.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.94/16.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.94/16.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.94/16.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.77/18.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.77/18.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.77/18.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.55/20.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.55/20.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.55/20.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.25/22.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.25/22.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.25/22.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.97/24.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.97/24.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.97/24.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.60/26.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.60/26.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.60/26.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.58/29.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.58/29.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.58/29.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.39/31.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.39/31.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.39/31.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.13/33.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.13/33.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.13/33.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.89/35.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.89/35.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.89/35.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.42/37.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.42/37.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.42/37.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.92/39.22  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.92/39.22  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.92/39.22  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.66/41.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.66/41.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.66/41.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.37/43.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.37/43.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.37/43.66  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.08/45.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.08/45.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.08/45.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.77/47.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.77/47.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.77/47.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.37/49.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.37/49.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.37/49.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.11/51.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.11/51.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.11/51.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.77/53.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.77/53.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.77/53.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.45/55.99  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.45/55.99  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.45/55.99  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.24/58.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.24/58.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.24/58.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.86/60.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.86/60.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.86/60.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 51.58/62.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.58/62.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.58/62.21  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------