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