On Wed, 4 Oct 2006, Jan Beulich wrote:
>
> Again, a corrupt stack will not allow you getting reliable data out of the
> old unwinder either. Even worse when you consider a stack overflow and
> your request for range checks (or pointers into the stack) - you might not
> get a stack trace then at all.
Who cares?
Not getting data out of a corrupt stack isn't the problem.
Getting an OOPS is the problem.
Jan, did you follow the actual thread at all?
This is _not_ about getting "perfect data". This is about a dead machine
that was killed not by the original bug, but by the DEBUGGING CODE it
triggered.
In other words, in this case the debugging code made things harder to
debug. That's bad, bad, bad. That negates the whole point of having
debugging code in the first place.
In contrast, the old x86 (32-bit) stack dumper was damn safe. If the
original %esp was at all a valid pointer (and it had to be, since
otherwise you'd have gotten a double fault!), it would print out something
_without_ crapping all over the machine. Maybe it wouldn't print out
anything nice, but it would never make things WORSE.
See the difference?
Linus
-
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]
