From: Alan Modra <amodra@bigpond.net.au>
To: Andreas Schwab <schwab@suse.de>, gdb-patches@sourceware.org
Cc: binutils@sourceware.org
Subject: Re: PowerPC64 synthetic syms
Date: Wed, 24 May 2006 08:13:00 -0000 [thread overview]
Message-ID: <20060523233657.GA18928@bubble.grove.modra.org> (raw)
In-Reply-To: <jefyj1kkmx.fsf@sykes.suse.de>
On Tue, May 23, 2006 at 02:09:42PM +0200, Andreas Schwab wrote:
> Alan Modra <amodra@bigpond.net.au> writes:
>
> > Really, gdb should be looking up the function descriptor syms itself
> > instead of relying on a crutch like the synthetic syms, but the
> > following patch happens to cure gdb and makes sense in isolation.
> > Applying mainline and 2.17.
>
> I think you want to apply that to the gdb-6.5 branch as well.
Probably. I'll need an OK from the relevant gdb authority.
http://sources.redhat.com/ml/binutils/2006-05/msg00389.html
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2006-05-23 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 6:07 Alan Modra
2006-05-23 15:48 ` Andreas Schwab
2006-05-24 8:13 ` Alan Modra [this message]
2006-05-24 8: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=20060523233657.GA18928@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=schwab@suse.de \
/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).