From: "Neo Jia" <neojia@gmail.com>
To: gdb@gnu.org, gdb@sourceware.org
Cc: "Daniel Jacobowitz" <drow@false.org>
Subject: Re: Is add-symbol-files broken on 64bit? (Need help!!!)
Date: Fri, 18 Jul 2008 08:03:00 -0000 [thread overview]
Message-ID: <5d649bdb0807180102l6d453ed0rb2ba277812095e12@mail.gmail.com> (raw)
In-Reply-To: <5d649bdb0807180100u58ec702g2a79a43173736dc8@mail.gmail.com>
Sorry, re-send with plain-text.
Thanks,
Neo
On Fri, Jul 18, 2008 at 1:00 AM, Neo Jia <neojia@gmail.com> wrote:
>
> hi,
>
> I am using the gdb to debug Linux kernel module on x86-64 bit with a patched kernel (kgdb). Everything works fine for the kernel itself, I can break on any functions, and see the sources. But, I can't break on the symbols in the kernel module after it is loaded. I used the "add-symbol-files" to add the sections for that loadable module.
>
> The same setup works fine for 32bit and I even can see the symbols/sources by running gdb directly against the 64bit .ko file.
>
> Any suggestions? I am struggling with this question for a long time.
>
> Thanks,
> Neo
>
> --
> I would remember that if researchers were not ambitious
> probably today we haven't the technology we are using!
--
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!
next parent reply other threads:[~2008-07-18 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d649bdb0807180100u58ec702g2a79a43173736dc8@mail.gmail.com>
2008-07-18 8:03 ` Neo Jia [this message]
2008-07-21 0:26 ` Michael Snyder
2008-07-21 2:25 ` Neo Jia
2008-07-24 0:07 ` Neo Jia
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=5d649bdb0807180102l6d453ed0rb2ba277812095e12@mail.gmail.com \
--to=neojia@gmail.com \
--cc=drow@false.org \
--cc=gdb@gnu.org \
--cc=gdb@sourceware.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