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

View Problem - Process Solution

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

% Computer : n003.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:52 EDT 2022

% Result   : Unknown 57.98s 70.66s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.05/0.09  % Problem  : HWV065+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.05/0.09  % Command  : leancop_casc.sh %s %d
% 0.09/0.29  % Computer : n003.cluster.edu
% 0.09/0.29  % Model    : x86_64 x86_64
% 0.09/0.29  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.09/0.29  % Memory   : 8042.1875MB
% 0.09/0.29  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.09/0.29  % CPULimit : 300
% 0.09/0.29  % WCLimit  : 600
% 0.09/0.29  % DateTime : Fri Jun 17 03:26:12 EDT 2022
% 0.09/0.29  % CPUTime  : 
% 2.61/2.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.61/2.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.61/2.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.97/5.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.97/5.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.97/5.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.52/8.87  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.52/8.87  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.52/8.87  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.01/11.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.01/11.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.01/11.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.47/15.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.47/15.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.47/15.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.90/18.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 14.90/18.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.90/18.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.38/21.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.38/21.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.38/21.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.80/24.31  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.80/24.31  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.80/24.31  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 23.39/28.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 23.39/28.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 23.39/28.54  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.17/30.78  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.17/30.78  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.17/30.78  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.01/33.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.01/33.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.01/33.04  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.73/35.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.73/35.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.73/35.00  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.43/37.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.43/37.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.43/37.01  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.18/39.13  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.18/39.13  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.18/39.13  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.98/41.24  *** Overflow of the global/trail stack in spite of garbage collection!
% 33.98/41.24  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.98/41.24  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.73/43.34  *** Overflow of the global/trail stack in spite of garbage collection!
% 35.73/43.34  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.73/43.34  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.25/45.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 37.25/45.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.25/45.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.67/47.12  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.67/47.12  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.67/47.12  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.37/49.53  *** Overflow of the global/trail stack in spite of garbage collection!
% 40.37/49.53  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.37/49.53  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 42.07/51.51  *** Overflow of the global/trail stack in spite of garbage collection!
% 42.07/51.51  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.07/51.51  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 44.00/53.77  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.00/53.77  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.00/53.77  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 45.85/55.83  *** Overflow of the global/trail stack in spite of garbage collection!
% 45.85/55.83  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.85/55.83  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 47.42/57.65  *** Overflow of the global/trail stack in spite of garbage collection!
% 47.42/57.65  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 47.42/57.65  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.35/59.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 49.35/59.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.35/59.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 51.03/61.89  *** Overflow of the global/trail stack in spite of garbage collection!
% 51.03/61.89  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.03/61.89  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 52.67/63.91  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.67/63.91  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.67/63.91  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 54.39/66.05  *** Overflow of the global/trail stack in spite of garbage collection!
% 54.39/66.05  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 54.39/66.05  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 56.20/68.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 56.20/68.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.20/68.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 57.89/70.18  *** Overflow of the global/trail stack in spite of garbage collection!
% 57.89/70.18  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 57.89/70.18  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------