From: Stefani Seibold <stefani@seibold.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix PPC floating point debug
Date: Fri, 27 Nov 2009 13:44:19 +0100 [thread overview]
Message-ID: <1259325859.21806.7.camel@wall-e> (raw)
In-Reply-To: <1259319716.2076.3.camel@pasglop>
Am Freitag, den 27.11.2009, 22:01 +1100 schrieb Benjamin Herrenschmidt:
> On Fri, 2009-11-27 at 09:59 +0100, Stefani Seibold wrote:
> > The PPC architecture is unable to debug applications using hardware
> > floating point, because it would not save the floating point registers.
> >
> > After returning from the debugger, the contents of register was
> > modified. This patch fix this bug.
>
> I'm not sure what problem you are trying to fix... debugging FP apps
> works just fine afaik. You don't need to flush the FP state into the
> thread when delivering the SIGTRAP. If you have a signal handler, that
> will be done for you by the signal code before laying out the signal
> frame. If you are using ptrace, you should be using the appropriate
> ptrace calls to retrieve the FP state and they should do the right thing
> to.
>
Aeh... Forget it! Thank you for the support.
Stefani
WARNING: multiple messages have this Message-ID (diff)
From: Stefani Seibold <stefani@seibold.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] fix PPC floating point debug
Date: Fri, 27 Nov 2009 13:44:19 +0100 [thread overview]
Message-ID: <1259325859.21806.7.camel@wall-e> (raw)
In-Reply-To: <1259319716.2076.3.camel@pasglop>
Am Freitag, den 27.11.2009, 22:01 +1100 schrieb Benjamin Herrenschmidt:
> On Fri, 2009-11-27 at 09:59 +0100, Stefani Seibold wrote:
> > The PPC architecture is unable to debug applications using hardware
> > floating point, because it would not save the floating point registers.
> >
> > After returning from the debugger, the contents of register was
> > modified. This patch fix this bug.
>
> I'm not sure what problem you are trying to fix... debugging FP apps
> works just fine afaik. You don't need to flush the FP state into the
> thread when delivering the SIGTRAP. If you have a signal handler, that
> will be done for you by the signal code before laying out the signal
> frame. If you are using ptrace, you should be using the appropriate
> ptrace calls to retrieve the FP state and they should do the right thing
> to.
>
Aeh... Forget it! Thank you for the support.
Stefani
next prev parent reply other threads:[~2009-11-27 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 8:59 [PATCH] fix PPC floating point debug Stefani Seibold
2009-11-27 11:01 ` Benjamin Herrenschmidt
2009-11-27 11:01 ` Benjamin Herrenschmidt
2009-11-27 12:44 ` Stefani Seibold [this message]
2009-11-27 12:44 ` Stefani Seibold
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=1259325859.21806.7.camel@wall-e \
--to=stefani@seibold.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.