Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, bauerman@br.ibm.com, amodra@bigpond.net.au
Subject: Re: Shared library call problems on PowerPC with current 	binutils/gdb
Date: Tue, 29 Apr 2008 03:05:00 -0000	[thread overview]
Message-ID: <20080429003951.GA30324@caradoc.them.org> (raw)
In-Reply-To: <200804282253.m3SMrwQF005602@d12av02.megacenter.de.ibm.com>

On Tue, Apr 29, 2008 at 12:53:58AM +0200, Ulrich Weigand wrote:
> - Extend elf_symtab_read to treat a synthetic symbol XXX@plt as a
>   mst_solib_trampoline symbol for XXX.

Sounds reasonable.  I suggested this to Aleksandar for another
problem, even :-) Though it was kind of nice to have it show up in
disassembly with @plt; will it still do that?  It's nice to know
immediately when I'm looking at the PLT stub instead of the
definition.

> - Change elf_symtab_read to register symbols with version name
>   simply under their base name.
> 
> - Include something along the lines of Markus' "multiply-defined
>   symbol" patch so that "break printf" will break on *both* definitions
>   (created by the two symbols with different version names) after libc
>   has been loaded.
> 
> - Teach minsym_found about function descriptors.

These sound like a good idea to me.

> - Add extra unwinders to ppc-linux-tdep that recognize the various
>   PLT call and glink stubs, and properly treat them as frameless.
>   (This will probably require code reading ...)
> 
> - Extend ppc_skip_trampoline_code to likewise handle those stubs.

These too, but it would be nice if we could avoid code reading all
the time.  Maybe only do it for symbols without a name or where
the defining symbol has size zero?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-04-29  0:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29  2:38 Ulrich Weigand
2008-04-29  3:05 ` Daniel Jacobowitz [this message]
2008-04-29 15:59   ` Daniel Jacobowitz
2008-05-02 23:01   ` Daniel Jacobowitz
2008-05-02 23:25     ` Ulrich Weigand
2008-05-03 15:39       ` Daniel Jacobowitz
2008-05-03 15:59         ` Ulrich Weigand
2008-05-03 17:19           ` Daniel Jacobowitz
2008-05-14 18:25             ` Ulrich Weigand
2008-05-14 18:29               ` Daniel Jacobowitz
2008-05-14 21:38                 ` Ulrich Weigand

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=20080429003951.GA30324@caradoc.them.org \
    --to=drow@false.org \
    --cc=amodra@bigpond.net.au \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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