On 07/28/2010 12:08 PM, Frederic Weisbecker wrote: > On Mon, Jul 26, 2010 at 07:13:23PM +0800, DDD wrote: > >> Frederic Weisbecker wrote: >> >>> Why? It seems to me a kernel debugger should have the highest priority >>> over anything. >>> >> In my option, the reason of kgdb set the lowest-prio for >> notifier is: >> >> For letting kgdb to keep simple, there is no codes to check the >> breakpoint event was generated by kgdb or not, thus it have to set kgdb >> as lowest priority to notifier. >> >> If the breakpoint event is not generated by kgdb, the source of the >> breakpoint event will consume that event before passing to kgdb's >> routine, so that the breakpoint event of kgdb getting must be generated >> by kgdb itself. >> > > > > Ok, but that makes it hard to differentiate from a spurious breakpoint > event. > > > >
The original thinking was that if you are using a low level debugger that you would want to stop on such a event or breakpoint because there is nothing else handling it and your system is about to print an oops message. Jason. ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
