From: Jim Blandy <jimb@codesourcery.com>
To: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
Cc: gdb@sourceware.org, drow@false.org
Subject: Re: DWARF question
Date: Fri, 28 Sep 2007 23:49:00 -0000 [thread overview]
Message-ID: <m34pheqt6u.fsf@codesourcery.com> (raw)
In-Reply-To: <46FD7AE9.8030208@linux.vnet.ibm.com> (Carlos Eduardo Seo's message of "Fri, 28 Sep 2007 19:06:33 -0300")
Carlos Eduardo Seo <cseo at linux.vnet.ibm.com> writes:
> Jim Blandy wrote:
>> The real question here is, why isn't find_line_symtab doing its job?
>> Its comment says:
>>
>> /* Find line number LINE in any symtab whose name is the same as
>> SYMTAB.
>>
>> If found, return the symtab that contains the linetable in which
> it was
>> found, set *INDEX to the index in the linetable of the best entry
>> found, and set *EXACT_MATCH nonzero if the value returned is an
>> exact match.
>>
>> If not found, return NULL. */
>>
>> That sounds to me like it's meant to address exactly the case we have
>> here. Could you take a look and tell us what you find?
>>
> Good point Jim. I'll take a look at that. The only thing I noticed in
> that function is that best_index always returns -1 when I try to set a
> breakpoint by line number in that function. I'm going deeper into that
> now.
>
> One point I forgot to mention and I think it's relevant is that when I
> load the binary with option '-readnow', that breakpoint by line number
> in the function works.
What probably happens is that '-readnow' somehow affects the order in
which the full symtabs get put in the list. I'm surprised that
breakpoints by line number in both main and the function work, but I
guess that has something to do with the nature of the bug in
find_line_symtab.
next prev parent reply other threads:[~2007-09-28 23:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 21:25 Carlos Eduardo Seo
2007-09-26 21:27 ` Daniel Jacobowitz
2007-09-27 8:29 ` Carlos Eduardo Seo
2007-09-28 20:26 ` Carlos Eduardo Seo
2007-09-28 21:13 ` Jim Blandy
2007-09-28 23:14 ` Carlos Eduardo Seo
2007-09-28 23:49 ` Jim Blandy [this message]
2007-10-01 17:49 ` Carlos Eduardo Seo
2007-10-02 19:15 ` Jim Blandy
2007-10-02 19:26 ` Carlos Eduardo Seo
2007-10-02 21:43 ` Carlos Eduardo Seo
2007-10-02 23:05 ` Carlos Eduardo Seo
2007-10-02 20:03 ` Jim Blandy
2007-10-02 20:09 ` Jim Blandy
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=m34pheqt6u.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=cseo@linux.vnet.ibm.com \
--cc=drow@false.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