From: Andrew Stubbs <ams@codesourcery.com>
To: Mike Frysinger <vapier@gentoo.org>
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 13:17:00 -0000 [thread overview]
Message-ID: <4D08BFFA.3010401@codesourcery.com> (raw)
In-Reply-To: <AANLkTinhK1SVv=Ymd53DE8JOo86cyrndKx6fVD03_Y8+@mail.gmail.com>
On 15/12/10 12:55, Mike Frysinger wrote:
> 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
Seems fine to me.
> 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.
I had not planned to submit it until I had the whole thing working.
Given that the kernel was badly broken, last time I checked, I couldn't
do it then, and I haven't had time since. Nor am I likely to have time
to do more work on this in the foreseeable future.
Feel free to take the patch and do what you like with it. It's just a
matter of cutting out the non-gdbserver bits anyway.
Andrew
next prev parent reply other threads:[~2010-12-15 13:17 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 ` [toolchain-devel] " Mike Frysinger
2010-12-15 13:17 ` Andrew Stubbs [this message]
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=4D08BFFA.3010401@codesourcery.com \
--to=ams@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=toolchain-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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