Bug#275023: g++-3.4: valgrind reports vectors don't free their memory

Hi Moritz I am having the same problem with g++ Version 4:3.3.5-3 but using dmalloc instead of valgrind. Specifically, I have a local vector in a subroutine. Before the subroutine returns I resize the vector to 0 (which shouldn't be necessary anyways). When the program is over I get the follwin

Bug#275023: g++-3.4: valgrind reports vectors don't free their memory

Hey, sorry for not responding for such a long time. I've upgraded to valgrind 3.0 and g++ 3.4.5, and valgrind does not report these leaks anymore. So the issue's been solved. Mosu -- If Darl McBride was in charge, he'd probably make marriage unconstitutional too, since clearly it de-emphasizes

Bug#275023: g++-3.4: valgrind reports vectors don't free their memory

tags 275023 + moreinfo thanks Hi, this is most likely spurious. Can you please read the valgrind hints at http://gcc.gnu.org/onlinedocs/libstdc++/debug.html and retry? -- Falk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE