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

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : HWV091+1 : TPTP v8.1.2. Released v6.1.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n024.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:10 EDT 2023

% Result   : Unknown 232.80s 228.97s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.13  % Problem  : HWV091+1 : TPTP v8.1.2. Released v6.1.0.
% 0.07/0.15  % Command  : nanocop.sh %s %d
% 0.16/0.36  % Computer : n024.cluster.edu
% 0.16/0.36  % Model    : x86_64 x86_64
% 0.16/0.36  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.16/0.36  % Memory   : 8042.1875MB
% 0.16/0.36  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.16/0.36  % CPULimit : 300
% 0.16/0.36  % WCLimit  : 300
% 0.16/0.36  % DateTime : Fri May 19 03:43:21 EDT 2023
% 0.16/0.36  % CPUTime  : 
% 24.52/23.73  *** Overflow of the global/trail stack in spite of garbage collection!
% 24.52/23.73  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 24.52/23.73  Peak sizes were: global stack 124696 kbytes, trail stack 6376 kbytes
% 48.85/47.66  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.85/47.66  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.85/47.66  Peak sizes were: global stack 124696 kbytes, trail stack 6376 kbytes
% 72.67/71.03  *** Overflow of the global/trail stack in spite of garbage collection!
% 72.67/71.03  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 72.67/71.03  Peak sizes were: global stack 124696 kbytes, trail stack 6376 kbytes
% 90.50/89.04  *** Overflow of the global/trail stack in spite of garbage collection!
% 90.50/89.04  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 90.50/89.04  Peak sizes were: global stack 126360 kbytes, trail stack 4840 kbytes
% 114.49/112.64  *** Overflow of the global/trail stack in spite of garbage collection!
% 114.49/112.64  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 114.49/112.64  Peak sizes were: global stack 124696 kbytes, trail stack 6376 kbytes
% 138.52/136.57  *** Overflow of the global/trail stack in spite of garbage collection!
% 138.52/136.57  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 138.52/136.57  Peak sizes were: global stack 124696 kbytes, trail stack 6376 kbytes
% 166.13/163.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 166.13/163.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 166.13/163.95  Peak sizes were: global stack 126360 kbytes, trail stack 4840 kbytes
% 232.71/228.36  *** Overflow of the global/trail stack in spite of garbage collection!
% 232.71/228.36  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 232.71/228.36  Peak sizes were: global stack 124696 kbytes, trail stack 6376 kbytes
% 232.80/228.97  Timeout
%------------------------------------------------------------------------------