Peter Steele pste...@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.
___
I've moved this to freebsd-hackers...
-Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Peter Steele
Sent: Thursday, March 25, 2010 9:54 PM
To: freebsd-questions@freebsd.org
Subject: Very suspicious stack trace
We had
We had an app crash and the resulting core dump produced a very
suspicious/confusing stack trace:
#0 0x0008011d438c in thr_kill () from /lib/libc.so.7
#1 0x0008012722bb in abort () from /lib/libc.so.7
#2 0x0008011fb70c in malloc_usable_size () from /lib/libc.so.7
#3
