Bug 361504

Summary: dlopen()/dlclose() and shared object usage check
Product: [Developer tools] valgrind Reporter: Eugene Zelenko <eugene.zelenko>
Component: memcheckAssignee: Julian Seward <jseward>
Status: REPORTED ---    
Severity: wishlist CC: ivosh
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Eugene Zelenko 2016-04-07 17:41:08 UTC 
I encountered situation when shared library was opened dlopen(), dlsym() was use to get function pointer, that function register function and data addresses in global data structure, dlclose() was called, but functions and data from shared library were used after that.

I'll be great if Valgrind will detect such invalid coding patterns, but I'm not sure if dl allow to get data/code segments addresses as well as reserve closed segments from re-using for later check in Valgrind.