On Sep 25, 2003, at 10:20 AM, Pedro Andujar wrote:
****BOX INFO****
[EMAIL PROTECTED] uname -a
Linux diablo.digitalsec.net 2.4.22-grsec #8 Mon Sep 22 07:42:09 PDT 2003 i686 athlon i386 GNU/Linux
[EMAIL PROTECTED] cat /etc/redhat-release
Red Hat Linux release 9 (Shrike)
[EMAIL PROTECTED] rpm -qa | grep tcpdu
tcpdump-3.7.2-1.9.1
[EMAIL PROTECTED] rpm -qa | grep pcap libpcap-0.7.2-1 [EMAIL PROTECTED]
...
[(gdb) info stack #0� 0x40118ecf in getifaddrs () from /lib/i686/libc.so.6
That looks like a bug in RH 9's "getifaddrs()", which recent versions of libpcap will use.
However, just in case it's a bug in libpcap, try getting the current CVS versions of libpcap and tcpdump from http://www.tcpdump.org (look for "Current Tar files"), unpacking them into the same directory (meaning that there should be libpcap and tcpdump directories in that directory; it doesn't mean put the actual libpcap and tcpdump source files in the same directory, it means put the libpcap and tcpdump source directories under the same directory), configuring and building libpcap, and configuring and building tcpdump.
If it still crashes, send us the stack trace (although it'll probably be crashing in "getifaddrs()", in which case it's probably a Red Hat bug) and the output of "tcpdump -h".
If it doesn't crash, then check whether there's a "fad-getad.o" file in the libpcap source directory. If not, libpcap somehow wasn't built to use "getifaddrs()"; run the configure script and send us the output. If so, this might be a bug with Red Hat's libpcap, so ask them about it.
- This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]
