[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUUkEgv+e1q3v1kW5WhJdT1egZKc5o96zF2omcT0YtVE3w@mail.gmail.com>
Date: Tue, 9 Apr 2013 15:06:39 +0200
From: Sedat Dilek <sedat.dilek@...il.com>
To: Jason Wessel <jason.wessel@...driver.com>
Cc: kgdb-bugreport@...ts.sourceforge.net,
LKML <linux-kernel@...r.kernel.org>
Subject: kdb: kgdb: CONFIG_DEBUG_RODATA setting?
>From [1]:
"If the architecture that you are using supports the kernel option
CONFIG_DEBUG_RODATA, you should consider turning it off. This option
will prevent the use of software breakpoints because it marks certain
regions of the kernel's memory space as read-only. If kgdb supports it
for the architecture you are using, you can use hardware breakpoints
if you desire to run with the CONFIG_DEBUG_RODATA option turned on,
else you need to turn off this option."
"Here is an example set of .config symbols to enable or disable for kgdb:
# CONFIG_DEBUG_RODATA is not set
CONFIG_FRAME_POINTER=y
CONFIG_KGDB=y
CONFIG_KGDB_SERIAL_CONSOLE=y
".
I am here on x86-64 and CONFIG_DEBUG_RODATA is always "=y" in
Linux-Next due to...
[ arch/x86/Kconfig.debug ]
config DEBUG_RODATA
bool "Write protect kernel read-only data structures"
default y
depends on DEBUG_KERNEL
So, is this setting now obsolete (means [1] not up2date?).
( See also my patch. )
Kind Regards,
- Sedat -
[1] https://www.kernel.org/pub/linux/kernel/people/jwessel/kdb/CompilingAKernel.html#CompileKGDB
Download attachment "0001-kdb-kgdb-x86-Unset-DEBUG_RODATA-when-KGDB.patch" of type "application/octet-stream" (1404 bytes)
Download attachment "config-3.9.0-rc6-next20130409-1-iniza-small" of type "application/octet-stream" (112103 bytes)
Powered by blists - more mailing lists