From: "Kris Warkentin" <kewarken@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: Interesting dwarf-2/shared lib problem.
Date: Tue, 02 Dec 2003 16:49:00 -0000 [thread overview]
Message-ID: <025701c3b8f4$6e1cfb70$0202040a@catdog> (raw)
In-Reply-To: <20031202161802.GA16598@nevyn.them.org>
> > I observed that libdisplay.so has been loaded with a psymtab and that
the
> > code in lookup_symtab() only searches through objects which have a full
> > symtab loaded. This would seem to be why it's not finding display.c.
I'm
> > supposing that when you do a break on a function, the full symtab is
then
> > loaded.
> >
> > Note also that this goes away if the source is compiled with the stabs+
> > debugging format. I'm pondering the solution to this. Is there a way
to
> > force gdb to load the full symbol table for all shared objects? Or is
there
> > a better way to get around this?
>
> >From lookup_symtab:
> /* Same search rules as above apply here, but now we look thru the
> psymtabs. */
>
> ps = lookup_partial_symtab (name);
> if (!ps)
> return (NULL);
>
> Is that not working?
Ah...interesting. For the main object, the symtab points to
c:\some_dir\main.c and the symtab->next points to just main.c. It's the
main.c that gets caught and returned. In the solib, we only see the
c:\some_lib\display.c so the FILENAME_CMP fails..
So you are correct, lookup_partial_symtab is failing.
cheers,
Kris
next prev parent reply other threads:[~2003-12-02 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 16:12 Kris Warkentin
2003-12-02 16:18 ` Daniel Jacobowitz
2003-12-02 16:49 ` Kris Warkentin [this message]
2003-12-02 17:11 ` Kris Warkentin
2003-12-02 17:17 ` Daniel Jacobowitz
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='025701c3b8f4$6e1cfb70$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/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