(2012/03/23 23:38), Jason Wessel wrote:
On 03/23/2012 09:08 AM, Masami Hiramatsu wrote:
(2012/03/22 20:57), Jason Wessel wrote:
I will use the arch specific provision to override the
kgdb_arch_set_breakpoint() and use the text_poke() directly.
Thanks! that's what I meant. You can use __weak
On 03/26/2012 04:46 AM, Masami Hiramatsu wrote:
(2012/03/23 23:38), Jason Wessel wrote:
On 03/23/2012 09:08 AM, Masami Hiramatsu wrote:
(2012/03/22 20:57), Jason Wessel wrote:
I will use the arch specific provision to override the
kgdb_arch_set_breakpoint() and use the text_poke() directly.
(2012/03/22 2:55), Jason Wessel wrote:
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
(2012/03/22 20:57), Jason Wessel wrote:
On 03/21/2012 09:53 PM, Masami Hiramatsu wrote:
(2012/03/22 2:55), Jason Wessel wrote:
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()
On 03/23/2012 09:08 AM, Masami Hiramatsu wrote:
(2012/03/22 20:57), Jason Wessel wrote:
I will use the arch specific provision to override the
kgdb_arch_set_breakpoint() and use the text_poke() directly.
Thanks! that's what I meant. You can use __weak attribute.
I created and tested a
On 03/21/2012 09:53 PM, Masami Hiramatsu wrote:
(2012/03/22 2:55), Jason Wessel wrote:
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
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
