Interface descriptions via pcap broken

Wesley Shields wxs at FreeBSD.org
Thu Mar 3 04:07:41 UTC 2011


On Wed, Mar 02, 2011 at 04:57:18PM -0600, Brandon Gooch wrote:
> On Wed, Mar 2, 2011 at 3:52 PM, Wesley Shields <wxs at 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 <jamesbrandongooch at 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@!

I've sent the patch along to someone with a src bit to commit. Hopefully
it ends up in the tree soon...

-- WXS


More information about the freebsd-net mailing list