From: Daniel Jacobowitz <dan@debian.org>
To: Laurent Vivier <LaurentVivier@wanadoo.fr>, linux-kernel@vger.kernel.org
Cc: Jeff Dike <jdike@addtoit.com>,
"Paolo 'Blaisorblade' Giarrusso" <blaisorblade_spam@yahoo.it>,
Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: PTRACE_SYSEMU numbering
Date: Wed, 21 Sep 2005 13:25:50 -0400 [thread overview]
Message-ID: <20050921172550.GA10332@nevyn.them.org> (raw)
Here's a bit of the PTRACE_SYSEMU patch, committed three weeks ago:
--- a/include/linux/ptrace.h
+++ b/include/linux/ptrace.h
@@ -20,6 +20,7 @@
#define PTRACE_DETACH 0x11
#define PTRACE_SYSCALL 24
+#define PTRACE_SYSEMU 31
/* 0x4200-0x4300 are reserved for architecture-independent additions. */
#define PTRACE_SETOPTIONS 0x4200
OK, I admit I could have made the comment clearer. But can we fix this?
You've added PTRACE_SYSEMU on top of PTRACE_GETFDPIC, which presumably will
mess up either debugging or UML on that architecture (if the latter were
ported). That's exactly the problem we defined the 0x4200-0x4300 range
to prevent.
--
Daniel Jacobowitz
CodeSourcery, LLC
next reply other threads:[~2005-09-21 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 17:25 Daniel Jacobowitz [this message]
2005-09-22 6:48 ` PTRACE_SYSEMU numbering Laurent Vivier
2005-09-22 19:46 ` Blaisorblade
2005-09-23 15:10 ` Daniel Jacobowitz
2005-10-06 19:23 ` Blaisorblade
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=20050921172550.GA10332@nevyn.them.org \
--to=dan@debian.org \
--cc=LaurentVivier@wanadoo.fr \
--cc=blaisorblade_spam@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.