From: Wenfeng Liu <wenfeng.liu@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [Questions] About experience of using kgdb for 2.6.10 kernel
Date: Mon, 19 Sep 2005 22:46:33 +0800 [thread overview]
Message-ID: <f8fda533050919074628ff140e@mail.gmail.com> (raw)
Hello, All
Recently I use kgdb for 2.6.10 kernel to debug driver modules. I got
the kgdb patch from kgdb CVS server. Here I have some experience of
using it with questions.
1. I use gdbmod-2.2 which is claimed to support automatically load
module symbol to correct address, but it don't do as that. I have to
manually add .text/.data/.bss sections address as add-symbol-file
parameters in gdb commands. Does anybody meet this?
2. I can't add one breakpiont for codes in symbol unless I stop in
sys_init_module and use "step" into module_init routine. It's not
convenient for module debugging, because every time I has to add
breakpoints in module_init, even I don't want to debug it. :(
3. The connection often hangs with printing "error packet" message
especially adding breakpoints or strike "n" quickly for multiple
times. And then the debug can't continue without restart.
Anyway, kgdb is a very good tool for kernel debugging. But from my
experience, it's not stable -- or my usage faults? Is anybody willing
to share with me his experience/knowledge?
Thanks much,
Kent
reply other threads:[~2005-09-19 14:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f8fda533050919074628ff140e@mail.gmail.com \
--to=wenfeng.liu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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