linux-kernel - Re: parsic/sh/sparc tracehook breakage when tracing signals

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100211.163950.206150918.davem@davemloft.net>
Date:	Thu, 11 Feb 2010 16:39:50 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	vapier@...too.org
Cc:	linux-sh@...r.kernel.org, linux-parisc@...r.kernel.org,
	sparclinux@...r.kernel.org, roland@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: parsic/sh/sparc tracehook breakage when tracing signals

From: Mike Frysinger <vapier@...too.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/