TSTP Solution File: HWV077+1 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : HWV077+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n023.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  : 300s
% DateTime : Fri May 19 11:18:07 EDT 2023

% Result   : Unknown 30.28s 41.91s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.13  % Problem  : HWV077+1 : TPTP v8.1.2. Bugfixed v5.5.1.
% 0.07/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.35  % Computer : n023.cluster.edu
% 0.13/0.35  % Model    : x86_64 x86_64
% 0.13/0.35  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35  % Memory   : 8042.1875MB
% 0.13/0.35  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.35  % CPULimit : 300
% 0.13/0.35  % WCLimit  : 300
% 0.13/0.35  % DateTime : Fri May 19 03:49:59 EDT 2023
% 0.13/0.35  % CPUTime  : 
% 1.64/1.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 1.64/1.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 1.64/1.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 2.98/3.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 2.98/3.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.98/3.74  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 4.70/6.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 4.70/6.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 4.70/6.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 6.14/7.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 6.14/7.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.14/7.98  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 7.93/10.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 7.93/10.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 7.93/10.35  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 9.35/12.08  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.35/12.08  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.35/12.08  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 10.79/14.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.79/14.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.79/14.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 12.23/16.27  *** Overflow of the global/trail stack in spite of garbage collection!
% 12.23/16.27  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.23/16.27  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 13.84/18.50  *** Overflow of the global/trail stack in spite of garbage collection!
% 13.84/18.50  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.84/18.50  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 15.64/20.75  *** Overflow of the global/trail stack in spite of garbage collection!
% 15.64/20.75  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.64/20.75  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.13/22.56  *** Overflow of the global/trail stack in spite of garbage collection!
% 17.13/22.56  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.13/22.56  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 18.61/24.60  *** Overflow of the global/trail stack in spite of garbage collection!
% 18.61/24.60  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.61/24.60  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 20.09/26.71  *** Overflow of the global/trail stack in spite of garbage collection!
% 20.09/26.71  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 20.09/26.71  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.56/28.76  *** Overflow of the global/trail stack in spite of garbage collection!
% 21.56/28.76  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.56/28.76  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.98/30.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.98/30.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.98/30.81  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 24.45/32.93  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.45/32.93  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.45/32.93  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 25.87/34.92  *** Overflow of the global/trail stack in spite of garbage collection!
% 25.87/34.92  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 25.87/34.92  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.38/37.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 27.38/37.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.38/37.03  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 28.79/39.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 28.79/39.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.79/39.09  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.22/41.17  *** Overflow of the global/trail stack in spite of garbage collection!
% 30.22/41.17  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.22/41.17  Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.28/41.91  Timeout
%------------------------------------------------------------------------------