This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug dynamic-link/19509] dlsym, dlvsym do not report errors through dlerror when using RTLD_NEXT
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 10 May 2016 11:42:09 +0000
- Subject: [Bug dynamic-link/19509] dlsym, dlvsym do not report errors through dlerror when using RTLD_NEXT
- Auto-submitted: auto-generated
- References: <bug-19509-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19509
--- Comment #5 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Peter Wu from comment #4)
> The regression happens due to use of malloc() in _dl_signal_error. This
> breaks interposing malloc libraries that encounter an unknown symbol (like
> ASAN). What about returning a generic error message or reverting this change?
I think the error message with and without RTLD_NEXT should be identical. We
could conceivably add a flag (say RTLD_NOERROR) which prevents setting an error
(dlsym/dlvsym would just return NULL). Please open a new bug for this.
(If you call dlsym, you really need to have a working malloc at that point.)
--
You are receiving this mail because:
You are on the CC list for the bug.