funny signal messages when tracing any app

[Dmitry V. Levin]

On Mon, May 13, 2013 at 07:08:57PM +0400, Dmitry V. Levin wrote:
> On Mon, May 13, 2013 at 05:04:36PM +0200, Denys Vlasenko wrote:
> > On 05/04/2013 11:21 PM, Dmitry V. Levin wrote:
> > > On Wed, May 01, 2013 at 11:04:13PM -0400, Mike Frysinger wrote:
> > >> i imagine this has to do with the probing of new ptrace features, but it still 
> > >> seems wrong for the first two lines to be signal stuff when tracing any program:
> > >> $ ./strace -eexecve /bin/true 
> > >> --- stopped by SIGSTOP ---
> > >> --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=10908, si_uid=8282} ---
> > > 
> > > These two lines are annoying, aren't they?
> > > It was discussed in February, with no visible result so far.
> > 
> > I will try to suppress them.
> 
> Another issue with USE_SEIZE is that -D option doesn't work:
> 
> $ env -i ./strace -D /bin/true
> ./strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted
> Alarm clock

Apparently, this is due to CONFIG_SECURITY_YAMA in default configuration,
it has nothing to do with PTRACE_SEIZE.  I'm testing the fix.


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20130513/9222346b/attachment.bin>