On Tue, 29 Apr 2008, Ingo Molnar wrote:

quoted text
> i pointed out how it should be done _much cleaner_ (and much smaller - 
> only a single patch needed) via stack-trace, without changing a dozen 
> architectures, and even gave a patch to make it all easier for you:
> 
>     http://lkml.org/lkml/2008/3/19/568
>     http://lkml.org/lkml/2008/3/21/88
> 
> in fact, a stacktrace printout is much more informative as well to 
> users, than a punny __builtin_return_address(0)!

Sorry lost track of this issue. Adding stracktrace support is not a 
trivial thing and will change the basic handling of vmallocinfo.

Not sure if stacktrace support can be enabled without a penalty on various 
platforms. Doesnt this require stackframes to be formatted in a certain 
way?

--
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/