This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Add finit_module syscall for Linux


>> I have no idea how to return -ESRCH if using pointer. Do you have?
>
> there's no requirement to do so; in fact, doing so is harmful because
> the code may seem to work (kill failing) but then signal the wrong
> thread if the same tid got reassigned to a new thread. any use of a
> pthtead_t after its lifetime is a serious programming error that is
> fundamentally undetectable, just like using a pointer to malloc'd
> memory after it was freed or using a pid aftef it was waited on.

Even though some one says "it's no requirement". Such applications don't
vanish. I agree id reassignment issue can be happen. however it doesn't
bring any happy to applications.

But anyway this is highly off topic. I have to stop hijack the thread.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]