On Wed, Jun 19, 2013 at 08:17:13PM +0400, Dmitry V. Levin wrote:
> On Wed, Jun 19, 2013 at 03:52:43PM +0200, Denys Vlasenko wrote:
> > V3: split SEIZE/!SEIZE code paths to reduce confusion.
>
> With your tests/detach* enhancements, I see persistent detach-stopped
> failures on old (!use_seize) kernels:
>
> $ cat detach-stopped.log
> FAIL: detach-stopped (exit: 1)
> ==============================
>
> Process 23456 attached
> --- SIGSTOP {si_signo=SIGSTOP, si_code=SI_USER, si_pid=0, si_uid=0} ---
> --- stopped by SIGSTOP ---
> restart_syscall(<... resuming interrupted call ...>Process 23456 detached
> <detached ...>
> State: S (sleeping)
> detach-stopped: failed test: tracee is not group-stopped after detach
>
> There is no such problem on recent kernels (tested on 3.9.6),
> both use_seize and !use_seize cases work.Of course, it is not a regression after your patch, this is how things work on those !use_seize kernels. If there is no way to workaround this, I suggest applying your patch. -- ldv
pgpj84ingoA8K.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Strace-devel mailing list Strace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/strace-devel
