kdb: Add message about CONFIG_DEBUG_RODATA on failure to install breakpoint
authorJason Wessel <jason.wessel@windriver.com>
Wed, 21 Sep 2011 20:07:47 +0000 (13:07 -0700)
committerJason Wessel <jason.wessel@windriver.com>
Thu, 22 Mar 2012 20:07:16 +0000 (15:07 -0500)
commit1ba0c1720eb0de2d0f3abf84c0b128d10af520d1
tree47515d331a39e868510266d72f29267b30b00399
parentb8adde8ddec9ff62a21564fa8020b5463e70d4de
kdb: Add message about CONFIG_DEBUG_RODATA on failure to install breakpoint

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 adds an printk message to the breakpoint failure case,
in order to provide suggestions about how to use the debugger.

Reported-by: Tim Bird <tim.bird@am.sony.com>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Acked-by: Tim Bird <tim.bird@am.sony.com>
kernel/debug/kdb/kdb_bp.c