From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Tighten and tweak ptrace argument checks
Date: Mon, 26 Sep 2005 01:51:00 -0000 [thread overview]
Message-ID: <20050926015138.GG22284@nevyn.them.org> (raw)
In-Reply-To: <200509181035.j8IAZjPV008619@elgar.sibelius.xs4all.nl>
[Eliding most of this, sorry...]
On Sun, Sep 18, 2005 at 12:35:45PM +0200, Mark Kettenis wrote:
> I'll be happy to simply weed out the obsolete PTRACE_XXX defs from
> config/ for the ports that I can't test. Of course that means risking
> potentially breaking those ports. Thus far we have been rather
> conservative about doing such things.
I'd rather do it than not...
> So, yes, I think it'd be good if you could still change things such
> that the n32 ptrace API would be identical to the o32 and n64 APIs.
> If not, I think the patch below is a low-risk way to check for the
> right prototype on n32 MIPS Linux.
I'm working on the API/ABI changes.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-09-26 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 21:28 Daniel Jacobowitz
2005-09-12 21:48 ` Mark Kettenis
2005-09-14 14:43 ` Daniel Jacobowitz
2005-09-18 10:36 ` Mark Kettenis
2005-09-26 1:51 ` Daniel Jacobowitz [this message]
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=20050926015138.GG22284@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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