diff options
| author | Jason Wessel <jason.wessel@windriver.com> | 2008-08-01 08:39:34 -0500 |
|---|---|---|
| committer | Jason Wessel <jason.wessel@windriver.com> | 2008-08-01 08:39:34 -0500 |
| commit | 5f5ddfb3605d2a4f555a7ff034859e623eafcd27 (patch) | |
| tree | f3a79d9f0ba631ed8d5e10560ab6cca2debe2f65 /Documentation/DocBook | |
| parent | 94ad374a0751f40d25e22e036c37f7263569d24c (diff) | |
kgdb: remove the requirement for CONFIG_FRAME_POINTER
There is no technical reason that the kgdb core requires frame
pointers. It is up to the end user of KGDB to decide if they need
them or not.
[ anemo@mba.ocn.ne.jp: removed frame pointers on mips ]
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Diffstat (limited to 'Documentation/DocBook')
| -rw-r--r-- | Documentation/DocBook/kgdb.tmpl | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/DocBook/kgdb.tmpl b/Documentation/DocBook/kgdb.tmpl index e8acd1f0345..54d3b158d08 100644 --- a/Documentation/DocBook/kgdb.tmpl +++ b/Documentation/DocBook/kgdb.tmpl @@ -98,6 +98,14 @@ "Kernel debugging" select "KGDB: kernel debugging with remote gdb". </para> <para> + It is advised, but not required that you turn on the + CONFIG_FRAME_POINTER kernel option. This option inserts code to + into the compiled executable which saves the frame information in + registers or on the stack at different points which will allow a + debugger such as gdb to more accurately construct stack back traces + while debugging the kernel. + </para> + <para> Next you should choose one of more I/O drivers to interconnect debugging host and debugged target. Early boot debugging requires a KGDB I/O driver that supports early debugging and the driver must be |