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

View Problem - Process Solution

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

% Computer : n029.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 52.22s 65.89s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.13  % Problem  : HWV074+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.08/0.14  % Command  : leancop_casc.sh %s %d
% 0.14/0.35  % Computer : n029.cluster.edu
% 0.14/0.35  % Model    : x86_64 x86_64
% 0.14/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.35  % Memory   : 8042.1875MB
% 0.14/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.14/0.35  % CPULimit : 300
% 0.14/0.35  % WCLimit  : 600
% 0.14/0.35  % DateTime : Fri Jun 17 08:36:28 EDT 2022
% 0.14/0.35  % CPUTime  : 
% 1.93/2.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.93/2.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.93/2.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.59/4.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.59/4.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.59/4.04  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.25/6.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.25/6.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.25/6.19  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.93/8.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.93/8.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.93/8.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.69/10.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.69/10.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.69/10.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.33/12.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.33/12.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.33/12.36  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.05/14.47  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.05/14.47  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.05/14.47  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.72/16.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.72/16.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.72/16.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.43/18.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.43/18.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.43/18.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.13/20.68  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.13/20.68  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.13/20.68  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.83/22.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.83/22.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.83/22.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.43/24.85  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.43/24.85  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.43/24.85  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.24/27.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.24/27.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.24/27.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.90/29.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.90/29.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.90/29.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.59/31.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.59/31.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.59/31.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.36/33.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.36/33.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.36/33.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.10/35.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.10/35.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.10/35.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.95/37.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.95/37.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.95/37.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.54/39.40  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.54/39.40  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.54/39.40  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.32/41.59  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.32/41.59  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.32/41.59  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.11/43.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.11/43.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.11/43.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.88/45.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.88/45.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.88/45.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.55/47.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.55/47.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.55/47.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.33/49.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.33/49.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.33/49.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.03/51.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.03/51.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.03/51.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.76/54.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.76/54.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.76/54.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.74/57.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.74/57.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.74/57.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.51/60.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.51/60.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.51/60.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.29/62.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.29/62.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.29/62.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 52.17/65.52  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.17/65.52  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.17/65.52  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------