From: Jim Blandy <jimb@codesourcery.com>
To: Jon Ringle <jon@ringle.org>
Cc: Jon Ringle <JRingle@vertical.com>, gdb@sourceware.org
Subject: Re: No line number info debugging kernel modules with gdb 6.6.90.20070926-cvs (gdb 6.7 branch)
Date: Fri, 28 Sep 2007 21:32:00 -0000 [thread overview]
Message-ID: <m3odfmqysb.fsf@codesourcery.com> (raw)
In-Reply-To: <46FC7961.2080706@ringle.org> (Jon Ringle's message of "Thu, 27 Sep 2007 23:47:45 -0400")
Jon Ringle <jon@ringle.org> writes:
> Jim Blandy wrote:
>> Hum. What do 'maint info psymtabs' and 'maint info symtabs' say after
>> you've set the breakpoint?
>>
> Trying to send the attachment again...
Okay, I got a copy of that attachment; thanks.
Could you start GDB, set the breakpoint and try listing the function
again, then do 'maint print symbols SOME-FILE dstchar.c' (or
perhaps use the full pathname for dstchar.c), and then post the
contents of SOME-FILE?
If GDB has line number information for that compilation unit, then
find_pc_sect_line ought to be able to find the source line for your
function's PC. I'd like to see whether it does have that information.
next prev parent reply other threads:[~2007-09-28 21:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 20:11 Jon Ringle
2007-09-28 0:25 ` Jim Blandy
2007-09-28 3:47 ` Jon Ringle
2007-09-28 13:47 ` Jon Ringle
2007-09-28 16:01 ` Jon Ringle
2007-09-28 21:32 ` Jim Blandy [this message]
2007-09-28 22:06 ` ringlej
2007-09-29 0:27 ` Jim Blandy
2007-09-29 0:27 ` Daniel Jacobowitz
2007-09-29 2:06 ` Jon Ringle
2007-09-29 2:27 ` Daniel Jacobowitz
2007-09-29 7:38 ` Jon Ringle
2007-10-02 21:38 ` Jim Blandy
2007-10-02 22:54 ` Jon Ringle
2007-10-02 20:26 ` Jim Blandy
2007-10-02 20:43 ` Daniel Jacobowitz
2007-09-29 1:28 ` Jon Ringle
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=m3odfmqysb.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=JRingle@vertical.com \
--cc=gdb@sourceware.org \
--cc=jon@ringle.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