X-Mailer: MIME-tools 5.508 (Entity 5.508)
MIME-Version: 1.0
Message-ID: <rt-4.4.1-97913-1515674598-1297.46841-0-0@isc.org>
X-RT-Original-Encoding: utf-8
Content-Transfer-Encoding: binary
X-RT-Interface: Web
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <rt-4.4.1-361-1515673336-1002.46841-0-0@isc.org>
References: <RT-Ticket-46841@isc.org>
 <5a3073d68c236_601632732824454@ss1435.mail>
 <rt-4.4.1-47768-1514935301-1679.46841-4-0@isc.org>
 <rt-4.4.1-97913-1515672797-245.46841-4-0@isc.org>
 <24AAAF10-397B-44AB-B6FE-A94948AD2885@isc.org>
 <rt-4.4.1-361-1515673336-1002.46841-0-0@isc.org>
RT-Send-CC:
Content-Length: 439

Thank you for this, it does shed some light on these warnings.  So it
complains that if I declare an array the way I do and then, somewhere
else, I attempt to access the element at index NS_QUERY_HOOKS_COUNT
(which I never do, but Coverity does not know that), it will be
out-of-bounds?

If that is the case, I would just size the arrays using the original
enum value (NS_QUERY_HOOKS_COUNT) + 1, i.e. without renaming the last
enum value.