general_protection result to die
hi; does general_protection trap necessarily result to die ? when executing this instruction : mov (%eax),%gs ,$ip turns to be general_protection. then it comes to debug() I have no clue for what has happend leads kernel to go here . it denotes what? Are there some adices here? thanks!
On Tue, 26 Feb 2013 06:23:34 +0800, horseriver said:
does general_protection trap necessarily result to die ?
Think for a bit - what other actions can reasonably be taken? You hit a GPF, it's obvious that the variables you're working on have been corrupted, so automatically continuing is probably a Really Bad Idea. If there's a debugger involved (gdb/kgdb), you can hand it to the (presumed) person running the debugger and let *them* figure out what to do, but that's about the only other realistic option.
participants (2)
-
horseriver -
Valdis.Kletnieks＠vt.edu