From: David Miller <davem@davemloft.net>
To: vapier@gentoo.org
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:39:50 +0000 [thread overview]
Message-ID: <20100211.163950.206150918.davem@davemloft.net> (raw)
In-Reply-To: <201002111910.50596.vapier@gentoo.org>
From: Mike Frysinger <vapier@gentoo.org>
Date: Thu, 11 Feb 2010 19:10:47 -0500
> 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.
next prev parent reply other threads:[~2010-02-12 0:39 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 [this message]
2010-02-12 0:56 ` Mike Frysinger
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=20100211.163950.206150918.davem@davemloft.net \
--to=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 \
--cc=vapier@gentoo.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).