From: Mike Frysinger <vapier@gentoo.org>
To: Andrew Stubbs <ams@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH]: gdb: fdpic/frv: fix shared library loading
Date: Thu, 15 Apr 2010 21:56:00 -0000 [thread overview]
Message-ID: <201004151622.03290.vapier@gentoo.org> (raw)
In-Reply-To: <4BC72FC1.7020401@codesourcery.com>
[-- Attachment #1: Type: Text/Plain, Size: 1971 bytes --]
On Thursday 15 April 2010 11:24:49 Andrew Stubbs wrote:
> On 14/04/10 07:59, Mike Frysinger wrote:
> > While I have no way of testing the FRV, the Blackfin FDPIC code is using
> > this same base in a 100% copy& paste method since we implemented FDPIC
> > the same way as the FRV guys (I'll address this in the future). This
> > fix was required in order to handle shared libraries with Blackfin FDPIC
> > properly, and I see no reason why it wouldn't also work for FRV (since
> > the uClibc ldso FDPIC code is the same too and that's really what this
> > is poking).
>
> I'm currently working on FDPIC support for SH-2A uClinux, so I have been
> poking at this same area myself.
>
> The FRV code would not work for me out of the box - it's a little too
> FRV specific, so I started work on another copy and paste, but thought
> better of it.
>
> What I've got now is the bones of a solib-fdpic.c which is intended to
> be architecture independent. This should be possible since, so far, all
> the FDPIC Linux implementations I've seen use the same basic ABI, and
> the SH FDPIC will follow suit.
sad, because ive already done the same thing and it's working for Blackfin
FDPIC. but we've implemented FDPIC the same was as FRV.
> The first major departure from solib-frv.c is that I've implemented a
> new qXfer remote protocol packet to retrieve the load maps (a pseudo
> register did not seem like a good plan). This should be target
> independent also - I believe FRV has the same ptrace interface as SH, so
> it should Just Work.
i posted a Linux patch a while ago to move the FDPIC ptrace defines out of the
arch-specific code and into the common ptrace code. it was acked by everyone,
but i guess i need to push andrew to merge it.
i dont have a problem with a pseudo register for the loadmaps ... seems like a
simple/straightforward way of getting the info rather than having to extend
the gdb protocol.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-04-15 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 7:00 Mike Frysinger
2010-04-15 15:25 ` Andrew Stubbs
2010-04-15 21:56 ` Mike Frysinger [this message]
2010-04-16 22:22 ` Kevin Buettner
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=201004151622.03290.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=ams@codesourcery.com \
--cc=gdb-patches@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