This is the mail archive of the glibc-bugs@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]

[Bug nptl/25158] warning when using non-thread-safe functions


https://sourceware.org/bugzilla/show_bug.cgi?id=25158

--- Comment #8 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Carlos O'Donell from comment #7)
>> There is also an unresolved ambiguity regarding what thread safety means for
>> function that updates objects whose address has been passed as parameters.
> 
> Can you give an exmaple of such a function? Are we talking about APIs like
> strtok?

I think “MT-Safe race:obstack-ptr” is such an example.

>> In the past, some of functions which only operate on their arguments have
>> been considered as not thread-safe. I don't think this particular approach
>> to thread safety is useful.
> 
> Could you expand on this please?

readdir vs readdir_r is the canonical example where things went really, really
wrong.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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