On Wed, Nov 14, 2007 at 03:41:43PM -0800, David Miller wrote:
quoted text > From: Matt Mackall <mpm@selenic.com>
> Date: Wed, 14 Nov 2007 17:37:13 -0600
>
> > No, the usual strategy for debugging problems -outside- SLOB is to
> > switch to another allocator with more extensive debugging facilities.
>
> Ok, so the thing we still can do is do a dump_stack() at the
> list debugging assertion trigger points.
It's also pretty easy to add some debugging code to make SLOB walk all
its lists at alloc/free time.
--
Mathematics is the supreme nostalgia of our time.
-
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: [bug] SLOB crash, 2.6.24-rc2 , Matt Mackall , (Wed Nov 14, 8:09 pm)