Bug 291380 - valgrind does not know memory of a shared object that was closed
Summary: valgrind does not know memory of a shared object that was closed
Status: RESOLVED DUPLICATE of bug 79362
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 3.7.0
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-12 16:02 UTC by viric
Modified: 2012-01-12 16:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description viric 2012-01-12 16:02:01 UTC 
Version:           3.7.0
OS:                Linux

Debugging code with some dlopen() and dlclose(), if there is some reference to an address of the dlopen()ed code (function pointer, data, etc..) referenced *after* a dlclose(), valgrind simply says that the address is totally unknown to him (not stack, not heap, ...).

valgrind knew, before dlclose(), what address was that. It would be nice if valgrind could report that the address may reference a dlclose()d shared object.

Reproducible: Always



Expected Results:  
It would be nice if valgrind could report that the address may reference a dlclose()d shared object.
Comment 1 Tom Hughes 2012-01-12 16:09:09 UTC 

*** This bug has been marked as a duplicate of bug 142086 ***
Comment 2 Tom Hughes 2012-01-12 16:10:52 UTC 

*** This bug has been marked as a duplicate of bug 79362 ***