Subject: tcpdump gets a bus error
To: None <port-sparc64@netbsd.org>
From: Frank Cusack <fcusack@fcusack.com>
List: port-sparc64
Date: 11/12/2002 12:22:19
[root@moltar]# tcpdump -n not tcp port 22
tcpdump: listening on hme0
...
Bus error (core dumped)
Nov 12 12:07:30 moltar /netbsd: Alignment error: pid=454 comm=tcpdump dsfsr=00000000:00800001 dsfar=0:3b61e7 isfsr=00000000:00000000 pc=10adf0

This consistently occurs after < 1 minute of running (same error).  Is
this likely to be a hardware problem, or a tcpdump 64-bitness problem?
I would guess the latter.

I can send a core file to anyone who's interested.  Here's a stack trace,
perhaps not so helpful:

(gdb) where
#0  0x10adf0 in dladdr ()
#1  0x10abd4 in dladdr ()
#2  0x11a53c in dladdr ()
#3  0x10fff0 in dladdr ()
#4  0x40321fac in pcap_read () from /usr/lib/libpcap.so.1
#5  0x403224cc in pcap_loop () from /usr/lib/libpcap.so.1
#6  0x134410 in main ()
#7  0x1023ac in _init ()

BTW, how do I build the system libraries with debugging symbols?

thanks
/fc