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

[salwen.1@osu.edu]

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 follwing from
in my logfile from dmalloc.  I believe the problem is in the vector
library function.

1129273462: 730: dumping not-freed pointers changed since 0:
1129273462: 730:  not freed: '0x6000000000028008|s1' (1280 bytes) from 'unknown'
1129273462: 730:  not freed: '0x6000000000038008|s1' (5200 bytes) from 'unknown'
1129273462: 730:  total-size  count  source
1129273462: 730:           0      0  Total of 0
1129273462: 730:  unknown memory: 2 pointers, 6480 bytes
1129273462: 730: ending time = 1129273462, elapsed since start = 0:00:00