* Andrew Morton <[email protected]> wrote:
> On Fri, 2 Jun 2006 09:09:48 +0200
> Ingo Molnar <[email protected]> wrote:
>
> > In all other cases (if we go outside of the stack page(s)) we _must_
> > fall back to the dump 'scan the stack pages for interesting entries'
> > method, to get the information out! "Uh oh the unwind info somehow got
> > corrupted, sorry" is not enough to debug a kernel bug.
>
> Also, it might be worth doing a two-pass thing. Pass 1 doesn't print
> anything - it just figures out whether pass2 will succeed. If not,
> fall back without printing anything.
correct, that's what stacktrace.c does for example. In the first lockdep
queue i switched show_trace() to make use of stacktrace.c, so it can be
used for printing traces too.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
