From: Arnd Bergmann <arnd@arndb.de>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: Tobias Klauser <tklauser@distanz.ch>,
Chung-Ling Tang <cltang@codesourcery.com>,
Walter Goossens <waltergoossens@home.nl>,
Ley Foon Tan <lftan@altera.com>,
linux-arch@vger.kernel.org,
"nios2-dev@lists.rocketboards.org"
<nios2-dev@lists.rocketboards.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: nios2: is the ptrace ABI correct?
Date: Tue, 24 Feb 2015 09:54:10 +0100 [thread overview]
Message-ID: <5636312.0WGrbVlVgB@wuerfel> (raw)
In-Reply-To: <CAAEAJfDjDYY-Z6cPyrddCXiFJzrjNx8jkSAJZuokeEM9NU6WWg@mail.gmail.com>
On Tuesday 24 February 2015 00:04:21 Ezequiel Garcia wrote:
> So, tried a different approach and removed pt_regs from the UAPI ptrace.h,
> replacing it with a new user_regs that describes how registers are passed
> to user. This however is also problematic, as pt_regs is already used
> by glibc (not really sure what for).
>
I've looked at glibc and could not find a use for pt_regs there. Where
did you find it? It's quite possible that it's incorrect as well
if the structures don't match.
Arnd
next prev parent reply other threads:[~2015-02-24 8:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 3:04 Ezequiel Garcia
2015-02-24 8:54 ` Arnd Bergmann [this message]
2015-02-24 15:28 ` Ezequiel Garcia
2015-02-24 19:25 ` Arnd Bergmann
2015-02-25 11:33 ` Ezequiel Garcia
2015-02-25 14:07 ` Arnd Bergmann
2015-02-27 8:57 ` Chung-Lin Tang
2015-02-27 11:19 ` Ezequiel Garcia
2015-03-04 20:56 ` Ezequiel Garcia
2015-03-09 16:54 ` Chung-Lin Tang
2015-03-09 17:02 ` Chung-Lin Tang
2015-03-09 17:05 ` Ezequiel Garcia
2015-03-10 2:54 ` Ley Foon Tan
2015-03-10 6:17 ` Chung-Lin Tang
2015-03-11 7:48 ` Ley Foon Tan
2015-03-11 14:31 ` Ezequiel Garcia
2015-03-12 11:07 ` Tobias Klauser
-- strict thread matches above, loose matches on Subject: below --
2015-02-24 2:30 Ezequiel Garcia
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=5636312.0WGrbVlVgB@wuerfel \
--to=arnd@arndb.de \
--cc=cltang@codesourcery.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=lftan@altera.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nios2-dev@lists.rocketboards.org \
--cc=tklauser@distanz.ch \
--cc=waltergoossens@home.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
all inboxes | Powered by JetHome®