From: Daniel Jacobowitz <drow@false.org>
To: Fabian Cenedese <Cenedese@indel.ch>
Cc: gdb@sourceware.org
Subject: Re: Symbols in same range
Date: Wed, 13 Dec 2006 18:13:00 -0000 [thread overview]
Message-ID: <20061213181325.GA13536@nevyn.them.org> (raw)
In-Reply-To: <5.2.0.9.1.20061213092734.01881ec0@NT_SERVER>
On Wed, Dec 13, 2006 at 09:44:47AM +0100, Fabian Cenedese wrote:
> Hi
>
> Is it correct to have several symbols in the same symtab range? Like:
Yes, this is not uncommon. For instance, if one source file defines
linkonce routines or functions in multiple sections.
I have worked on several problems related to this one lately. Are you
using GDB HEAD? If not, does it do any better? Does the patch in this
message help?
http://sourceware.org/ml/gdb-patches/2006-12/msg00005.html
> find_pc_sect_psymtab, pc=0x99928
> lookup_minimal_symbol_by_pc_section
> -> msymbol="_INI_0200_INOS"
> tpst='Inos_mod.cpp'
> find_pc_sect_psymbol
> -> p="CEnd"
> -> ps='Inos_mod.cpp'
> -> s='Inos_mod.cpp'
> best_symtab=NULL
> -> .line=0
>
> The found msymbol is always correct, but when gdb continues to find
> the corresponding block it takes the symtab from a wrong file. But the
> addresses in there don't match (only the range) and the returned
> result is .line=0.
There should be a psymbol in the correct psymtab which is closer to the
specified pc. What symbols are at or directly before that location?
> Is this an error in the finding strategy of gdb, like, it should look
> in all symtabs and not only in the first whose range matches?
It should find the correct psymtab. You'll see that
find_pc_sect_psymtab actually loops over them all.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-12-13 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 8:46 Fabian Cenedese
2006-12-13 18:13 ` Daniel Jacobowitz [this message]
2006-12-14 9:51 ` Fabian Cenedese
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=20061213181325.GA13536@nevyn.them.org \
--to=drow@false.org \
--cc=Cenedese@indel.ch \
--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