From: Keith Owens <kaos@ocs.com.au>
To: Paul J Albrecht <pjalbrecht@home.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Debuggers, KDB or KGDB?
Date: Thu, 03 May 2001 09:03:55 +1000 [thread overview]
Message-ID: <5003.988844635@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Wed, 02 May 2001 16:06:15 EST." <01050216532701.00700@CB57534-A>
On Wed, 2 May 2001 16:06:15 -0500,
Paul J Albrecht <pjalbrecht@home.com> wrote:
>I'd like to know more about your plans to enhance KDB with source level debug
>capability.
Use a combination of gdb and kdb. kdb to support kernel internals, gdb
to take the kdb output and add source level data. It needs two
machines, one that is running to support gdb, the second machine is
being debugged, with a serial console between them.
The problem will be stopping gdb from making assumptions about the
machine being debugged. Instead of changing gdb code, use a gdb
wrapper program to intercept user commands and gdb serial protocol and
convert them to kdb commands.
>Would you have to boot an unstripped kernel executable whenever you
>wanted to debug?
Boot, no. But the machine running gdb will need an copy of the
unstripped vmlinux and module objects to get the debug information.
next prev parent reply other threads:[~2001-05-02 23:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 21:17 Linux Kernel Debuggers, KDB or KGDB? Paul J Albrecht
2001-05-01 0:11 ` Jeff Dike
2001-05-01 9:37 ` Ingo Oeser
2001-05-01 15:22 ` Jeff Dike
2001-05-02 14:44 ` Ingo Oeser
2001-05-02 17:54 ` Jeff Dike
2001-05-02 16:55 ` Alan Cox
2001-05-02 19:06 ` Jeff Dike
2001-05-02 18:54 ` Bill Nottingham
2001-05-01 1:16 ` Keith Owens
2001-05-01 10:59 ` Amit S. Kale
2001-05-02 14:58 ` Andi Kleen
2001-05-02 21:06 ` Paul J Albrecht
2001-05-02 23:03 ` Keith Owens [this message]
2001-05-03 14:46 ` Amit S. Kale
[not found] <linux.kernel.18223.988679810@kao2.melbourne.sgi.com>
2001-05-01 7:13 ` Aaron Passey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5003.988844635@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pjalbrecht@home.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox