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

2024-12-06 Thread Kees Bakker via bind-users
On 04-12-2024 18:52, Ondřej Surý wrote: Kees, I would suggest to ask your supplier to fix this. 9.16.23 is not only on the 9.16 EOL branch, but it is not even latest 9.16 release[*]. That would be 9.16.50, chances are that your issue has been already fixed. Or it is caused by the dyndb-ldap p

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

2024-12-05 Thread Kees Bakker via bind-users
On 04-12-2024 21:41, Petr Špaček wrote: [...] It sounds like you are able to reproduce it fairly easily, right? Yes, fairly easy. If that's the case I would recommend running `named` under RR debugger. In case you are not familiar with it have a look at https://rr-project.org/ - it is an _awe

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

2024-12-04 Thread Petr Špaček
On 04. 12. 24 17:31, Kees Bakker wrote: On 03-12-2024 15:56, Petr Špaček wrote: On 03. 12. 24 11:36, Kees Bakker via bind-users wrote: 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_equ

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

2024-12-04 Thread Ondřej Surý
Kees, I would suggest to ask your supplier to fix this. 9.16.23 is not only on the 9.16 EOL branch, but it is not even latest 9.16 release[*]. That would be 9.16.50, chances are that your issue has been already fixed. Or it is caused by the dyndb-ldap plugin. Debugging 9.16.23+pile_of_patches

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

2024-12-04 Thread Kees Bakker via bind-users
On 03-12-2024 15:56, Petr Špaček wrote: On 03. 12. 24 11:36, Kees Bakker via bind-users wrote: 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 absol

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

2024-12-03 Thread Petr Špaček
On 03. 12. 24 11:36, Kees Bakker via bind-users wrote: 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 i

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

2024-12-03 Thread 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 > wrote: > > Hi, > > Background > I hav

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

2024-12-03 Thread Kees Bakker via bind-users
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