Date: Fri, 26 Mar 2010 00:55:15 -0700 From: perryh@pluto.rain.com To: psteele@maxiscale.com Cc: freebsd-questions@freebsd.org Subject: Re: Very suspicious stack trace Message-ID: <4bac6863.tRIjBQNjM5YzAEsl%perryh@pluto.rain.com> In-Reply-To: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3B5AAC95@MBX03.exg5.exghost.com> References: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3B5AAC95@MBX03.exg5.exghost.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Steele <psteele@maxiscale.com> wrote: > what would lead malloc() into calling abort()? > Everything seems to be in order. Something may have trashed its internal data structures. I'd suggest a close look for things like buffer overflows.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4bac6863.tRIjBQNjM5YzAEsl%perryh>