[Bug time/29705] libc timer_create with option SIGEV_THREAD system call having memory leaks after timer_delete system call

["fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>]

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
We don't really know if all but one thread have been stopped when
__libc_freeres is called by the leak detector. valgrind does this, but other
callers might not or might not have the capability to do that because Linux
does not provide it.

If those threads are still running, bad things will happen if we free the DTV
and other per-thread data.

The best thing we can probably do here is not to use malloc to allocate DTVs
and other low-level per-thread data structures, effectively hiding these
allocations from the leak detector.

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