From: kirill@shutemov.name (Kirill A. Shutemov)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ptrace: system call number interpretation during PTRACE_SET_SYSCALL request handling
Date: Tue, 15 Sep 2009 12:37:59 +0300 [thread overview]
Message-ID: <cc557aab0909150237u451eaab0v82f08eb65ef706a2@mail.gmail.com> (raw)
In-Reply-To: <20080601083036.GD5818@flint.arm.linux.org.uk>
On Sun, Jun 1, 2008 at 11:30 AM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Fri, May 30, 2008 at 09:30:27PM +0300, Volodymyr G. Lukiianyk wrote:
>> I've encountered a problem while running strace on the kernel with
>> CONFIG_AEABI not set. This problem can be worked around in userspace,
>> but it looks like the correct place for a fix is the kernel.
>
> I'm really nervous about this. ?I need to check what my own strace
> patches do - and if they don't suffer from this problem I'd say that
> the bug lies in userspace.
Any results? Do we need to workaround it in user space or it will be
fixed in kernel?
> Yes, for a long time I've had patches to strace to add proper ARM
> support and fix a load of issues with it, but I've never been able
> to get them integrated into strace itself.
>
> -------------------------------------------------------------------
> List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
> FAQ: ? ? ? ?http://www.arm.linux.org.uk/mailinglists/faq.php
> Etiquette: ?http://www.arm.linux.org.uk/mailinglists/etiquette.php
>
next parent reply other threads:[~2009-09-15 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <484047C3.4090509@gmail.com>
[not found] ` <20080601083036.GD5818@flint.arm.linux.org.uk>
2009-09-15 9:37 ` Kirill A. Shutemov [this message]
2009-09-17 20:41 ` [RFC] ptrace: system call number interpretation during PTRACE_SET_SYSCALL request handling Kirill A. Shutemov
2009-09-17 20:52 ` Russell King - ARM Linux
2009-09-17 21:12 ` Kirill A. Shutemov
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=cc557aab0909150237u451eaab0v82f08eb65ef706a2@mail.gmail.com \
--to=kirill@shutemov.name \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).