From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [RFC/PATCH 5/5] powerpc: Allow ptrace write to pt_regs trap
Date: Wed, 30 May 2007 14:33:31 +1000 [thread overview]
Message-ID: <1180499611.19517.222.camel@localhost.localdomain> (raw)
In-Reply-To: <OFF7AF7C86.A40E5407-ON422572EA.00560C99-422572EA.00563CD2@de.ibm.com>
> This doesn't look sufficient. If you want GDB to use the save/
> restore style means of handling interrupted calls (like i386),
> at the very least we also need the capability to *write* the
> orig_gpr3 field, which is currently prohibited. (I don't know
> why this is case, though.)
Ok, I found it... put_reg doesn't filter it out but the caller does.
Fixing that too.
Ben.
prev parent reply other threads:[~2007-05-30 4:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 6:45 [RFC/PATCH 5/5] powerpc: Allow ptrace write to pt_regs trap Benjamin Herrenschmidt
2007-05-29 15:41 ` Ulrich Weigand
2007-05-29 21:41 ` Benjamin Herrenschmidt
2007-05-30 13:08 ` Ulrich Weigand
2007-05-30 4:33 ` Benjamin Herrenschmidt [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=1180499611.19517.222.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).