Date: Wed, 2 Mar 2011 16:52:58 -0500 From: Wesley Shields <wxs@FreeBSD.org> To: Bruce Cran <bruce@cran.org.uk> Cc: Brandon Gooch <jamesbrandongooch@gmail.com>, freebsd-net@freebsd.org, Rui Paulo <rpaulo@freebsd.org> Subject: Re: Interface descriptions via pcap broken Message-ID: <20110302215258.GA48643@atarininja.org> In-Reply-To: <20110302194540.0000018f@unknown> References: <1298961441.2888.2.camel@core.nessbank> <AANLkTik_JxT4G7SBsqEZYFvVDFJUFxzhmHaYj%2BrAN9P6@mail.gmail.com> <20110302194540.0000018f@unknown>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110302215258.GA48643>