From: Mike Frysinger <vapier@gentoo.org>
To: David Miller <davem@davemloft.net>
Cc: linux-sh@vger.kernel.org, linux-parisc@vger.kernel.org,
sparclinux@vger.kernel.org, roland@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: parsic/sh/sparc tracehook breakage when tracing signals
Date: Fri, 12 Feb 2010 00:56:03 +0000 [thread overview]
Message-ID: <201002111956.06261.vapier@gentoo.org> (raw)
In-Reply-To: <20100211.163950.206150918.davem@davemloft.net>
[-- Attachment #1: Type: Text/Plain, Size: 1033 bytes --]
On Thursday 11 February 2010 19:39:50 David Miller wrote:
> From: Mike Frysinger <vapier@gentoo.org>
> > when i ported the Blackfin code to the tracehook framework, i copied a
> > latent bug from the sparc port. trying to trace another process while
> > handling signals no longer worked (and subsequently broke some of the gdb
> > tests).
>
> What you seem to be missing is that on Sparc TIF_SINGLESTEP will never
> be set, because it does not support hardware single step.
>
> This thread flag is not even defined on that platform.
my point is that these arches never call ptrace_notify(SIGTRAP) from their
signal handlers. maybe the arch is unable to due to some port/hardware
limitation and this is currently the expected behavior.
dont get me wrong ... i dont particularly care if your arch has a bug in it
here. my arch did have a bug and on the off chance that others did too, i
thought i'd drop an e-mail to people. if your arch is in the "limited"
category, feel free to ignore this.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-02-12 0:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 0:10 parsic/sh/sparc tracehook breakage when tracing signals Mike Frysinger
2010-02-12 0:39 ` David Miller
2010-02-12 0:56 ` Mike Frysinger [this message]
2010-02-12 3:07 ` Roland McGrath
2010-02-12 15:09 ` Kyle McMartin
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=201002111956.06261.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=roland@redhat.com \
--cc=sparclinux@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 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).