https://bugs.kde.org/show_bug.cgi?id=361504
Bug ID: 361504 Summary: dlopen()/dlclose() and shared object usage check Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: eugene.zele...@gmail.com 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. -- You are receiving this mail because: You are watching all bug changes.