Red Hat Bugzilla – Bug 105335
bind 9.2.1-9 Segmentation Fault
Last modified: 2007-04-18 12:57:48 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
Description of problem:
Named segfaults when I run:
gdb stack trace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 8194 (LWP 2737)]
0x4007b4bd in getname () from /usr/lib/libdns.so.5
#0 0x4007b4bd in getname () from /usr/lib/libdns.so.5
#1 0x4007bd80 in getsection () from /usr/lib/libdns.so.5
#2 0x4007c8d8 in dns_message_parse () from /usr/lib/libdns.so.5
#3 0x400dfde0 in resquery_response () from /usr/lib/libdns.so.5
#4 0x4023f339 in dispatch () from /usr/lib/libisc.so.4
#5 0x4023f461 in run () from /usr/lib/libisc.so.4
#6 0x40275941 in pthread_start_thread () from /lib/i686/libpthread.so.0
#7 0x40275a45 in pthread_start_thread_event () from /lib/i686/libpthread.so.0
Version-Release number of selected component (if applicable):
I have a TCP dump at http://www.roaringpenguin.com/bind-crash.tcpdump that shows
the packets being exchanged. It was produced with "tcpdump -w"; you can open it
with Ethereal or tcpdump -r.
I rated this as "security" because a segfault in named makes me very, very, very
Created attachment 94705 [details]
Tcpdump of traffic that crashed bind-9.2.1-9
This tcpdump was created using "tcpdump -s 1500 -w filename -i ppp0 port 53"
You can look at it with ethereal or "tcpdump -r"
Never mind... my /usr/lib/libdns.so.5.0.3 had somehow become modified. I need
to figure out how, but reinstalling the RPM fixed it.