[Bug malloc/25533] dlopen with RTLD_DEEPBIND crashes when using custom memory manager

["Simon.Richter at hogyros dot de" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #7 from Simon Richter <Simon.Richter at hogyros dot de> ---
> This will only push the problem one layer further, in the sense that the caller of strdup would have to be duplicated as well.

In my case, the caller of the strdup is the object that was loaded with
RTLD_DEEPBIND, so that would be kind of what I'd expect here: if another copy
of libudev already exists in the process and is reused without making sure that
its internal references aren't overridden in the instance that is returned,
then the RTLD_DEEPBIND would be silently ignored.

Rereading the documentation of RTLD_DEEPBIND, I'm even slightly confused why
applying RTLD_DEEPBIND to an object will also pull the symbols of its
dependencies to the front (so glibc's "realloc" wins over libtbbmalloc's, as
libudev is only linked against glibc). I would have expected libudev's symbols
to take precedence for internal resolution, and then the same order as in the
rest of the program for the other symbols.

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