Prev: [GIT PULL] ceph fixes for 2.6.35
Next: linux-next: Tree for July 28 (lirc #2)
From: Jason Wessel on 28 Jul 2010 13:20
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [GIT PULL] ceph fixes for 2.6.35
Next: linux-next: Tree for July 28 (lirc #2)