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

2005-08-16 Thread Moritz Bunkus
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

2004-10-05 Thread Moritz Bunkus
Package: g++-3.4 Version: 3.4.2-2 Severity: normal Maybe this is not a bug in g++ but in valgrind, or maybe it isn't a bug at all, so my apologies if this is wrong here. Anyway. A program using std::vector compiled with g++-3.4 spits out a lot of warnings when it is run under valgrind with leak c