Q: drop PTRACE_SEIZE_DEVEL?

[Dmitry V. Levin]

On Tue, Jul 10, 2012 at 04:36:18PM +0200, Denys Vlasenko wrote:
> On 07/10/2012 01:01 AM, Dmitry V. Levin wrote:
[...]
> > I suppose we can safely drop PTRACE_SEIZE_DEVEL from USE_SEIZE code now.
> 
> I'm going to do that. Also will drop PTRACE_EVENT_STOP1
> and enable USE_SEIZE in defs.h

It seems to be working so far, but with annoying addition to the strace
output:

$ strace true
--- stopped by SIGSTOP ---
--- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=4096, si_uid=512} ---
execve("/bin/true", ["true"], [/* 32 vars */]) = 0
exit_group(0)                           = ?
+++ exited with 0 +++

The child process is actually being stopped and continued, but are these
technical details of USE_SEIZE implementation worth seeing?


-- 
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/20121031/203735af/attachment.bin>