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

View Problem - Process Solution

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

% Computer : n021.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:49 EDT 2022

% Result   : Unknown 43.77s 62.50s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.10/0.12  % Problem  : HWV058+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.10/0.12  % Command  : leancop_casc.sh %s %d
% 0.12/0.33  % Computer : n021.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 600
% 0.12/0.33  % DateTime : Fri Jun 17 06:56:45 EDT 2022
% 0.12/0.34  % CPUTime  : 
% 1.47/1.67  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.47/1.67  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.47/1.67  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.87/3.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.87/3.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.87/3.73  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.13/5.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.13/5.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.13/5.70  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.56/7.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.56/7.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.56/7.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.85/9.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.85/9.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.85/9.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.20/11.96  *** Overflow of the global/trail stack in spite of garbage collection!
% 8.20/11.96  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.20/11.96  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.62/14.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.62/14.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.62/14.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.02/16.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.02/16.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.02/16.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.40/18.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.40/18.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.40/18.16  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.76/20.28  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.76/20.28  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.76/20.28  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.13/22.29  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.13/22.29  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.13/22.29  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.63/24.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.63/24.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.63/24.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.96/26.49  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.96/26.49  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.96/26.49  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.48/28.63  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.48/28.63  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.48/28.63  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.96/30.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.96/30.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.96/30.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.36/32.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.36/32.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.36/32.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.88/34.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.88/34.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.88/34.84  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.24/36.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.24/36.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.24/36.90  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 26.73/38.94  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.73/38.94  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.73/38.94  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.14/41.07  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.14/41.07  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.14/41.07  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.61/43.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.61/43.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.61/43.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 31.20/45.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 31.20/45.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 31.20/45.31  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.79/47.42  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.79/47.42  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.79/47.42  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 34.32/49.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 34.32/49.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 34.32/49.48  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.89/51.58  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.89/51.58  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.89/51.58  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.52/53.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.52/53.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.52/53.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 39.05/55.69  *** Overflow of the global/trail stack in spite of garbage collection!
% 39.05/55.69  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.05/55.69  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.75/57.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.75/57.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.75/57.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.24/59.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.24/59.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.24/59.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.68/61.72  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.68/61.72  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.68/61.72  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------