But that in turn let me realize that the bug that "78543ad" was only introduced by "e24bc324".
So we won't backport "e24bc324" (which is a massive rework of the hash handling) just to fix it.
@Andreas - what do you think might this - despite the similarity - be a different issue after all. Maybe a different off-by-one/crash but in a similar place to look so similar?
If so do we have a crash dump of that fail that Marian reported to take a look?
I looked at the changes Andreas pointed to, but I'm unsure they are really the same right now.
- 0003-Print- diagnostics- on-dns_ name_issubdomai n-failure- in.patch
applied as-is, but is about diagnostics and not fixing a crash as reported here
- 0004-Fix- off-by- one-error- when-calculatin g-new-hashtable -.patch /github. com/isc- projects/ bind9/commit/ e24bc324b455d9c ad7b51acd3d5c7b 4e40c66187 /github. com/isc- projects/ bind9/commit/ 1e043a011b9fe3f 62f9f5c7a9b74b4 4adc03ca44
does not apply as-is
Tracking this I found this would also need (at least) the backport of:
https:/
https:/
But that in turn let me realize that the bug that "78543ad" was only introduced by "e24bc324".
So we won't backport "e24bc324" (which is a massive rework of the hash handling) just to fix it.
@Andreas - what do you think might this - despite the similarity - be a different issue after all. Maybe a different off-by-one/crash but in a similar place to look so similar?
If so do we have a crash dump of that fail that Marian reported to take a look?