24 Apr
2009
24 Apr
'09
6:21 p.m.
On Thu, Apr 23, 2009 at 09:36:23PM +0100, Jeremy Henty wrote:
On Thu, Apr 23, 2009 at 06:01:56PM +0200, Hofmann Johannes wrote:
It turns out that memory related to aborted images is not released.
What about the other way round, ie. memory being released and then accessed? If you check the invalid read errors at the valgrind logs page[1] for the past few days you will see they are all due to reading freed image memory. Is this another aspect of the same thing, or something else?
I'd say it's something different. It's always a read of size 4, isn't it? I guess that's just one uninitialized pointer. Cheers, Johannes