Sorry about replying to this old thread, but... On Mon, Apr 3, 2017 at 9:07 AM, Eric W. Biederman <ebiederm@xxxxxxxxxxxx> wrote: > I don't know who actually useses PTRACE_O_TRACEEXIT so I don't actually > know what the implications of changing it are. Let's see... > > gdb - no > upstart - no > lldb - yes > strace - no For the record, rr uses PTRACE_O_TRACEEXIT. When a thread exits we need to examine its address space to find its robust futex list and record the changes that will be performed by the kernel as it cleans up that list. So, any failures to deliver PTRACE_EVENT_EXIT are potentially problematic for us because we won't get a chance to examine the address space before it disappears. Rob -- lbir ye,ea yer.tnietoehr rdn rdsme,anea lurpr edna e hnysnenh hhe uresyf toD selthor stor edna siewaoeodm or v sstvr esBa kbvted,t rdsme,aoreseoouoto o l euetiuruewFa kbn e hnystoivateweh uresyf tulsa rehr rdm or rnea lurpr .a war hsrer holsa rodvted,t nenh hneireseoouot.tniesiewaoeivatewt sstvr esn -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
