Messages in this thread | | | Date | Tue, 29 Jan 2008 23:38:31 +0530 | From | "Abhishek Sagar" <> | Subject | Re: [PATCH 0/3][RFC] x86: Catch stray non-kprobe breakpoints |
| |
On 1/29/08, Masami Hiramatsu <mhiramat@redhat.com> wrote: > In that case, why don't you just reduce the priority of kprobe_exceptions_nb? > Then, the execution path becomes very simple.
Ananth mentioned that the kprobe notifier has to be the first to run. It still wouldnt allow us to notice breakpoints on places like do_int3 etc.
> I also like to use a debugger for debugging kprobes. that will help us.
Hmm...It would increase the code-path leading upto kprobe_handler. That's more territory to be guarded from kprobes.
> Best Regards, > > -- > Masami Hiramatsu > > Software Engineer > Hitachi Computer Products (America) Inc. > Software Solutions Division > > e-mail: mhiramat@redhat.com -- Thanks, Abhishek
| |