tcpdump crash on arm?

Olivier Houchard mlfbsd at ci0.org
Thu Apr 5 11:04:43 UTC 2007


On Thu, Apr 05, 2007 at 10:28:18AM +0300, Krassimir Slavchev wrote:
> Hi,
> 
> This is on 7.0-CURENT 4-5 days old but I have seen this for 2-3 months.
> 
> # ./tcpdump
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on ate0, link-type EN10MB (Ethernet), capture size 96 bytes
> Bus error (core dumped)
> 
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain 
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "arm-marcel-freebsd"...
> Core was generated by `tcpdump'.
> Program terminated with signal 10, Bus error.
> Reading symbols from /lib/libpcap.so.4...done.
> Loaded symbols for /lib/libpcap.so.4
> Reading symbols from /lib/libcrypto.so.5...done.
> Loaded symbols for /lib/libcrypto.so.5
> Reading symbols from /lib/libc.so.7...done.
> Loaded symbols for /lib/libc.so.7
> Reading symbols from /libexec/ld-elf.so.1...done.
> Loaded symbols for /libexec/ld-elf.so.1
> #0  0x000203a4 in ether_print ()
> (gdb) bt
> #0  0x000203a4 in ether_print ()
> #1  0x00020730 in ether_if_print ()
> #2  0x0005b594 in print_packet (user=0xbfffec18 "\020\a\002", h=0xbfffeb98,
>    sp=0x2040901a "")
>    at 
> /usr/src-arm/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/tcpdump.c:1241
> #3  0x200f05bc in pcap_lookupnet () from /lib/libpcap.so.4
> #4  0x200f1a2c in pcap_loop () from /lib/libpcap.so.4
> #5  0x0005c3b0 in $a ()
>    at 
> /usr/src-arm/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/tcpdump.c:1050
> #6  0x0005c3b0 in $a ()
>    at 
> /usr/src-arm/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/tcpdump.c:1050
> (gdb)
> 

I remember seeing this, but I thought make worlding fixed it.
Warner, do you remember what the issue was, and how/if we fixed it ?
I think it had to do with the change in alignment somewhere.

Olivier


More information about the freebsd-current mailing list