On Thu, 2008-04-24 at 14:14 +0200, stephane eranian wrote: > Petr, > > Thanks for checking, I am pretty sure this is a problem introduced recently. > The only thing related to this that I can think of is the TIF_RESTORE_RSE > and the associated TIF_NOTIFY_RESUME. > > When I try the same test on 2.6.25: Yes, this is consistent with what I can see on 2.6.25-rc3 (which I still had lying around on the test host): glass:~/ptrace-wrong-notify # ./task_ptrace_attach ./forktest 10 10 creating 10 additional process(es) 10 iterations pid=3006 errno=0 exited=0 stopped=1 signaled=0 stopsig=19 SIGSTOP from [3006] pid=3006 errno=0 exited=1 stopped=0 signaled=0 stopsig=0 EXITED [3006] pid=3005 errno=0 exited=0 stopped=1 signaled=0 stopsig=5 FORK new_pid [3006] and so on... Ok, I'm going to play with git now. ;] Petr Tesarik -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|