| commit | a5d10eb1f587a13a513504ffb5d8e6a8738eee6f | [log] [tgz] |
|---|---|---|
| author | Rich Felker <dalias@aerifal.cx> | Mon Apr 23 12:03:31 2012 -0400 |
| committer | Rich Felker <dalias@aerifal.cx> | Mon Apr 23 12:03:31 2012 -0400 |
| tree | a83002de87443fc6c9124288c3864595b6172735 | |
| parent | 90da74ef51ddd51924042ee42b5e766908e9980c [diff] |
make dlerror produce informative results note that dlerror is specified to be non-thread-safe, so no locking is performed on the error flag or message aside from the rwlock already held by dlopen or dlsym. if 2 invocations of dlsym are generating errors at the same time, they could clobber each other's results, but the resulting string, albeit corrupt, will still be null-terminated. any use of dlerror in such a situation could not be expected to give meaningful results anyway.