On Tue, Aug 30, 2005 at 07:50:31AM -0700, George Anzinger wrote:
> Tom Rini wrote:
[snip]
> >"no context" is the label we're in, in the code. What it's actually
> >used for is "hey, we (== kgdb) tried to read/write a very very bogus
> >addr, time to longjmp". If it's not true that kgdb is at fault then we
> >drop to the debugger anyhow, and the user can see where they came from.
> >
> No. What the user sees is the offending code (i.e. prior to the trap to
> page_fault), NOT how kgdb happend to be called. The "no_context" is IN
> the _context_ of page_fault, but that is lost by the time you get to
> kgdb and ask to see _why_ (via, hint, hint: "p kgdb_info").
So you're suggesting changing what we pass in so that if we also modify
kgdb_info to contain the 'where' thing you talked about before, it would
be more useful, yes? If so, I think that can wait just a bit. :)
--
Tom Rini
http://gate.crashing.org/~trini/
-
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |