Abhishek Sagar wrote: > Placing a breakpoint on kprobe_handler (say) can loop into a recursive > trap without allowing the debugger's notifier chain to be invoked. I'm > assuming that non-kprobe exception notifiers may (or even should) run > after kprobe's notifier callback (kprobe_exceptions_notify).
In that case, why don't you just reduce the priority of kprobe_exceptions_nb? Then, the execution path becomes very simple. int3 (non-kprobe) -> do_int3 -> non-krpobe/debugger I also like to use a debugger for debugging kprobes. that will help us. Best Regards, -- Masami Hiramatsu Software Engineer Hitachi Computer Products (America) Inc. Software Solutions Division e-mail: [EMAIL PROTECTED] -- 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/
