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

View Problem - Process Solution

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

% Computer : n032.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:57 EDT 2022

% Result   : Unknown 49.65s 62.36s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.05/0.09  % Problem  : HWV076+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.05/0.09  % Command  : leancop_casc.sh %s %d
% 0.08/0.28  % Computer : n032.cluster.edu
% 0.08/0.28  % Model    : x86_64 x86_64
% 0.08/0.28  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.08/0.28  % Memory   : 8042.1875MB
% 0.08/0.28  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.08/0.28  % CPULimit : 300
% 0.08/0.28  % WCLimit  : 600
% 0.08/0.28  % DateTime : Thu Jun 16 20:28:00 EDT 2022
% 0.08/0.28  % CPUTime  : 
% 1.76/1.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.76/1.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.76/1.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 3.41/3.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 3.41/3.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.41/3.95  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.08/6.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.08/6.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.08/6.02  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.74/8.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.74/8.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.74/8.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.33/10.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.33/10.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.33/10.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.01/12.25  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.01/12.25  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.01/12.25  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.69/14.30  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.69/14.30  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.69/14.30  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.40/16.37  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.40/16.37  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.40/16.37  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.03/18.43  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.03/18.43  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.03/18.43  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.77/20.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.77/20.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.77/20.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.40/22.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.40/22.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.40/22.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.08/24.61  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.08/24.61  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.08/24.61  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.72/26.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.72/26.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.72/26.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.38/28.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.38/28.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.38/28.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.03/30.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.03/30.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.03/30.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.65/32.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.65/32.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.65/32.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.32/35.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.32/35.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.32/35.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.01/37.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.01/37.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.01/37.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.67/39.10  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.67/39.10  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.67/39.10  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.24/41.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.24/41.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.24/41.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.01/43.32  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.01/43.32  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.01/43.32  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 36.59/45.23  *** Overflow of the global/trail stack in spite of garbage collection!
% 36.59/45.23  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.59/45.23  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.23/47.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.23/47.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.23/47.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.86/49.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.86/49.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.86/49.38  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.52/51.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.52/51.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.52/51.49  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.14/53.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.14/53.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.14/53.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.80/55.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.80/55.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.80/55.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 46.34/57.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 46.34/57.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 46.34/57.64  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 48.06/59.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.06/59.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.06/59.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.57/61.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.57/61.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.57/61.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------