On Sun, Jan 25, 2009 at 06:07:58PM +0100, Hofmann Johannes wrote:
I decided to stick with SimpleVector, but allocate CssSimpleSelector properly with new/delete. Please check current tip.
This seems to have fixed all the big "definitely lost" errors, which is very good. I still see some small "possibly lost" errors. The valgrind docs advise that "possibly lost" really means "definitely lost" unless you are doing something funny. I can't tell whether that applies here! As I understand it, "possibly lost" means that there is still a pointer to the interior of the block. Most likely the original pointer to the block has been lost and it has therefore leaked, but it is possible that the program knows about the interior pointer and is using that to access the block. Valgrind log attached. Regards, Jeremy Henty