public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Paul Koning <pkoning@equallogic.com>
To: drow@false.org
Cc: gdb@sources.redhat.com
Subject: Re: find_pc_partial_function may produce the wrong answer
Date: Wed, 20 Jul 2005 17:09:00 -0000	[thread overview]
Message-ID: <17118.34095.8510.304158@gargle.gargle.HOWL> (raw)
In-Reply-To: <20050720143326.GA31003@nevyn.them.org>

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

 Daniel> Is the shared library stripped?  I am absolutely positive
 Daniel> that the minimal symbol table will include the static symtab
 Daniel> - as long as there is one.

Found the problem.

The NetBSD build procedure for libraries has a rather peculiar compile
step, which includes running the file through ld with a -x switch.
That will do it...  It's not supposed to do that if a -g is present in
the compile options; that may be an error in the top level build
process at our end.

That does leave this puzzle:

Given such a shared library (no local symbols in the symtab),
"disassemble somestaticfunc" works fine if I open the shared lib
itself with gdb.  But if the shared lib is referenced via the shared
lib symbol load machinery, for example because a corefile pointed to
it, then the same disassemble command doesn't work.

It looks like the code in blockframe.c that pulls in the psymtab to
double-check the function (if an end address was requested) doesn't
work in that second case.  Does that make sense?

     paul

  parent reply	other threads:[~2005-07-20 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 14:28 Paul Koning
2005-07-20 14:33 ` Daniel Jacobowitz
2005-07-20 15:38   ` Paul Koning
2005-07-20 16:17     ` H. J. Lu
2005-07-20 16:24       ` Paul Koning
2005-07-20 17:09   ` Paul Koning [this message]
2005-07-20 17:13     ` 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=17118.34095.8510.304158@gargle.gargle.HOWL \
    --to=pkoning@equallogic.com \
    --cc=drow@false.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).