How to print details of dns_name_t* when hitting a gdb breakpoint in dns_name_equal

[Greg Choules]

Hi Kees.
I would upgrade to 9.18 and not spend time trying to diagnose 9.16, which is not supported anymore. If the same problem occurs on 9.18 (latest), please let us know.

I hope that helps.
Greg

> On 3 Dec 2024, at 10:36, Kees Bakker via bind-users <bind-users at lists.isc.org> wrote:
> 
> Hi,
> 
> Background
> I have a CentOS FreeIPA setup with with multiple named (bind9 9.16.23) servers.
> On two of my five servers, when I start named it fails a REQUIRE in dns_name_equal
> 
>     /*
>      * Either name1 is absolute and name2 is absolute, or neither is.
>      */
>     REQUIRE((name1->attributes & DNS_NAMEATTR_ABSOLUTE) ==
>         (name2->attributes & DNS_NAMEATTR_ABSOLUTE));
> 
> My question: if I run gdb and break in "assertion_failed", then "go up",
> how can I print name1 and name2 in a meaningful manner,
> so that I can figure out what entries are causing this failure?
> 
> Just doing "p *name1" in gdb isn't very helpful for that.
> 
> BTW My work around is to keep restarting named until it no longer fails
> on that REQUIRE.
> 
> Any help is greatly appreciated.
> -- Kees
> -- 
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
> 
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users