Bug 291380

Summary:	valgrind does not know memory of a shared object that was closed
Product:	[Developer tools] valgrind	Reporter:	viric <viric>
Component:	memcheck	Assignee:	Julian Seward <jseward>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	tom
Priority:	NOR
Version First Reported In:	3.7.0
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

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 ***