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
On 03/20/2012 04:31 PM, Tim Bird wrote:
> On 03/20/2012 11:32 AM, Jason Wessel wrote:
>> On 09/21/2011 03:07 PM, Tim Bird wrote:
>>> On x86, if CONFIG_DEBUG_RODATA is set, one cannot set breakpoints
>>> via KDB. Apparently this is a well-known problem, as at least one
>>> distribution
>>> now shi
On 03/20/2012 11:32 AM, Jason Wessel wrote:
> On 09/21/2011 03:07 PM, Tim Bird wrote:
>> On x86, if CONFIG_DEBUG_RODATA is set, one cannot set breakpoints
>> via KDB. Apparently this is a well-known problem, as at least one
>> distribution
>> now ships with both KDB enabled and CONFIG_DEBUG_RODAT
On 09/21/2011 03:07 PM, Tim Bird wrote:
> On x86, if CONFIG_DEBUG_RODATA is set, one cannot set breakpoints
> via KDB. Apparently this is a well-known problem, as at least one
> distribution
> now ships with both KDB enabled and CONFIG_DEBUG_RODATA=y for security
> reasons.
>
> This patch just
On x86, if CONFIG_DEBUG_RODATA is set, one cannot set breakpoints
via KDB. Apparently this is a well-known problem, as at least one distribution
now ships with both KDB enabled and CONFIG_DEBUG_RODATA=y for security reasons.
This patch just adds an extra printk message to the breakpoint failure c
