|
From: Tom H. <to...@co...> - 2005-08-12 11:05:43
|
In message <112...@sp...>
Dennis Lubert <pla...@in...> wrote:
> I currently work on an application where most of the code is loaded as
> plugins, and as a workaround I set a environment variable that tells the
> plugin mechanism to not dlclose() so that I have the symbols in the
> stack traces with valgrind. As I think lots of people use polymorphism
> for plugins have problems with this, so lots of people would benefit
> from a mechanism that keeps the symbols. The same is for different
> memory accesses... it would help if it could tell where it has been
> unmapped, or if it tells that its not stacked/malloced/freed but in this
> or that segment or similar. A tool like that should give as much
> information as possible, no matter if it seems helpful at first or not
> (thats why we have --verbose flags ;)
I wasn't talking about keeping the symbols - that would be nice but
working out how to do it efficiently is hard.
I was talking keeping a history of what memory had been recently
unmapped so that we could give the "this memory was recently released"
message that was asked for.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|