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

View Problem - Process Solution

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

% Computer : n015.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:54 EDT 2022

% Result   : Unknown 50.75s 62.65s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.13  % Problem  : HWV070+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.11/0.13  % Command  : leancop_casc.sh %s %d
% 0.13/0.34  % Computer : n015.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 02:05:57 EDT 2022
% 0.13/0.35  % CPUTime  : 
% 1.78/1.97  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.78/1.97  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.78/1.97  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.34/3.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.34/3.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.34/3.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.06/6.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.06/6.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.06/6.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.85/8.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.85/8.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.85/8.26  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.51/10.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.51/10.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.51/10.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.17/12.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.17/12.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.17/12.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.79/14.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.79/14.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.79/14.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.39/16.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.39/16.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.39/16.39  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.99/18.46  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.99/18.46  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.99/18.46  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.64/20.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.64/20.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.64/20.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.19/22.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.19/22.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.19/22.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.82/24.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.82/24.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.82/24.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.50/26.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.50/26.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.50/26.79  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.04/28.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.04/28.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.04/28.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.77/30.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.77/30.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.77/30.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.42/33.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.42/33.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.42/33.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.10/35.11  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.10/35.11  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.10/35.11  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.84/37.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.84/37.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.84/37.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.47/39.20  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.47/39.20  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.47/39.20  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.37/41.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.37/41.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.37/41.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.97/43.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.97/43.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.97/43.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.76/45.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.76/45.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.76/45.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.53/47.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.53/47.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.53/47.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.32/49.80  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.32/49.80  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.32/49.80  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.03/51.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.03/51.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.03/51.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.83/53.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.83/53.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.83/53.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.51/55.88  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.51/55.88  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.51/55.88  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.28/58.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.28/58.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.28/58.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.96/60.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.96/60.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.96/60.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.64/62.15  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.64/62.15  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.64/62.15  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------