On Wed, Mar 2, 2011 at 3:52 PM, Wesley Shields <w...@freebsd.org> wrote: > On Wed, Mar 02, 2011 at 07:45:40PM +0000, Bruce Cran wrote: >> On Wed, 2 Mar 2011 13:40:57 -0600 >> Brandon Gooch <jamesbrandongo...@gmail.com> wrote: >> >> > BTW, if you give your devices descriptions, libpcap >> > starts to behave again; this could be a clue to the source of the bug >> > :/ >> >> 0xa5 is the malloc fill pattern when debugging is enabled, and >> having recently reinstalled FreeBSD I forgot to create the malloc.conf >> symlink. So something's reading from uninitialized memory. > > Does commit c65292b04b98d6a76d58c5a54ca8f81463bf24de in the libpcap git > tree look like it could help? I haven't checked in detail but I think it > might have never made it into a release yet? > > https://github.com/mcr/libpcap/commit/c65292b04b98d6a76d58c5a54ca8f81463bf24de > > -- WXS
I applied the patch attached (diff'd against the code from the github link above), rebuilt libpcap and wireshark, and the problem described no longer exists. Thanks for looking at this wxs@! -Brandon
libpcap-inet.c.diff
Description: Binary data
_______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
