From: Mike Frysinger <vapier@gentoo.org>
To: Andrew Stubbs <ams@codesourcery.com>
Cc: Daniel Jacobowitz <dan@codesourcery.com>,
toolchain-devel@blackfin.uclinux.org,
gdb-patches@sourceware.org, Pedro Alves <pedro@codesourcery.com>
Subject: Re: [toolchain-devel] [PATCH v2] gdbserver: bfin: new port
Date: Wed, 15 Dec 2010 12:55:00 -0000 [thread overview]
Message-ID: <AANLkTinhK1SVv=Ymd53DE8JOo86cyrndKx6fVD03_Y8+@mail.gmail.com> (raw)
In-Reply-To: <4D08AC60.9060307@codesourcery.com>
On Wed, Dec 15, 2010 at 06:54, Andrew Stubbs wrote:
> On 14/12/10 17:25, Mike Frysinger wrote:
>>> I did start implementing something vaguely target independent (included
>>> > in CodeSourcery SG++), but the state of the SH-2A kernel debug support
>>> > put that project on the back burner, so it remains the bare minimum.
>>
>> i'm not asking for a finished project. i would like to simply review the
>> code
>> you said you have already. so where might one find your SuperH/FDPIC
>> gdb/gdbserver code ?
>
> The latest CodeSourcery SH-2A toolchain binaries and source can be
> downloaded from here:
> http://www.codesourcery.com/sgpp/lite/superh/portal/release1602
>
> I've attached my original patch. I didn't do the forward port when we
> updated GDB myself, so it may be out-of-date in a few places.
code looks good ... but there's one slight problem. it is binding to
the format gdbserver itself is being compiled as. in other words,
this code requires gdbserver itself to be compiled as FDPIC in order
to debug FDPIC applications. the current Blackfin code does not have
that restriction ... a FLAT gdbserver can debug a FDPIC app just fine.
but it seems this limitation is superfluous ... how about we change
the __FDPIC__ ifdef to:
#if defined(PTRACE_GETFDPIC_EXEC) && defined(PTRACE_GETFDPIC_INTERP)
...
#endif
do you have an idea of when you'll submit just the qXfer:fdpic support
? seems that these pieces can stand on their own just fine.
-mike
next prev parent reply other threads:[~2010-12-15 12:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 9:29 [PATCH v2] gdb: " Mike Frysinger
2010-12-09 9:31 ` [PATCH v2] gdbserver: " Mike Frysinger
2010-12-13 18:44 ` Pedro Alves
2010-12-13 19:24 ` Mike Frysinger
2010-12-14 9:37 ` Andrew Stubbs
2010-12-14 15:10 ` Mike Frysinger
2010-12-14 16:31 ` Pedro Alves
2010-12-14 16:58 ` Mike Frysinger
2010-12-14 17:16 ` Andrew Stubbs
2010-12-14 17:26 ` Mike Frysinger
2010-12-15 11:54 ` Andrew Stubbs
2010-12-15 12:55 ` Mike Frysinger [this message]
2010-12-15 13:17 ` [toolchain-devel] " Andrew Stubbs
2010-12-14 17:40 ` Pedro Alves
2010-12-14 17:48 ` Mike Frysinger
2010-12-14 18:06 ` Pedro Alves
2010-12-14 18:21 ` Mike Frysinger
2010-12-15 16:54 ` Mike Frysinger
2010-12-14 6:03 ` [PATCH v2] gdb: " Joel Brobecker
2010-12-14 16:14 ` Mike Frysinger
2010-12-14 20:43 ` [PATCH v3] " Mike Frysinger
2010-12-14 21:31 ` Pedro Alves
2010-12-14 22:01 ` Mike Frysinger
2010-12-15 13:02 ` Mike Frysinger
2010-12-15 16:53 ` Pedro Alves
2010-12-15 17:08 ` Mike Frysinger
2010-12-15 18:01 ` Pedro Alves
2010-12-15 18:38 ` Mike Frysinger
2010-12-15 18:42 ` Pedro Alves
2010-12-15 18:16 ` Mike Frysinger
2010-12-15 18:25 ` Pedro Alves
2010-12-14 21:48 ` [PATCH v3] gdbserver: " Mike Frysinger
2010-12-14 23:03 ` Ralf Corsepius
2010-12-15 0:15 ` Mike Frysinger
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='AANLkTinhK1SVv=Ymd53DE8JOo86cyrndKx6fVD03_Y8+@mail.gmail.com' \
--to=vapier@gentoo.org \
--cc=ams@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=toolchain-devel@blackfin.uclinux.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