Thanks for the bug report, Fedon.
I have tried reproducing the crash using the steps provided by you
(inside a Jammy amd64 container), but I got the same results as Lucas:
"dig google.com +nssearch" would hang there indefinitely, but won't
crash.
I was able to make it crash when I appended "+tcp" to the command:
# dig google.com +nssearch +tcp
dighost.c:1683: INSIST(query->readhandle == ((void *)0)) failed, back trace
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(+0x32083)[0x7f193d786083]
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(isc_assertion_failed+0x10)[0x7f193d785570]
...
but the assertion that's been triggered is different than the one you're
seeing.
Unfortunately there are several problems with dig on bind9 9.18.1, so
it's hard to determine if these two errors are the same. I'd like to
ask for your help in testing a possible fix for this problem. If I
prepare a PPA with a candidate fix, would you be able to give it a try
and let me know the results?
Thanks in advance.
** Also affects: bind9 (Ubuntu Kinetic)
Importance: Undecided
Status: Triaged
** Tags added: server-todo
** Changed in: bind9 (Ubuntu Jammy)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: bind9 (Ubuntu Kinetic)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970252
Title:
The `dig` and `host` commands core dump or give incomplete results in
Ubuntu 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1970252/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
