On 03/20/2012 04:55 PM, Jason Wessel wrote:
>
> Obviously we are not going to go down the horrible hack route, so I
> thought I might look at how the kprobe implementation works, because
> they do deal with read-only pages. They created a function called
> text_poke() that is called from arc
There is extra state information that needs to be exposed in the
kgdb_bpt structure for tracking whether or not a breakpoint was
installed via a kprobe or via a probe_kernel_write(). In order to
access the structure it needs to be passed to the
kgdb_arch_set_breakpoint() and kgdb_arch_remove_break
The inability to use software breakpoints on a kernel built with
CONFIG_DEBUG_RODATA has been a problem for quite a few years. The
kprobes API has been working around this limitation for a long
time. This patch set changes the debug_core to use the kprobe
breakpoint API directly for a kernel compi
There has long been a limitation using software breakpoints with a
kernel compiled with CONFIG_DEBUG_RODATA. The kprobe breakpoint code
has its own text_poke() function which accommodates writing a
breakpoint into a read-only page. The debug_core can make use of the
text_poke() capabilities by us
