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 network/10652] getaddrinfo causes segfault if multithreaded and linked statically


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

--- Comment #22 from Rich Felker <bugdal at aerifal dot cx> ---
As long as libpthread is a separate DSO, avoiding loading it makes sense, yes.
However it seems that all the internal locking in glibc components (including
nss modules) could be done with lock functions available unconditionally in
libc rather than needing the pthread lock functions. I'm not familiar enough
with the glibc internals to know whether such functions are already available,
but it would certainly make for a cleaner solution to this and many other
problems if they are. Note that the locking requirements for internal use are
much simpler than pthread requirements; there are no difficult issues like
different mutex types, self-synchronized destruction, etc.

-- 
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]