On Tue, May 5, 2009 at 1:45 AM, Miguel Ojeda <[email protected]> wrote: > On Mon, May 4, 2009 at 3:32 PM, fpga <[email protected]> wrote: >> >> #include "sstream" >> using namespace std; >> int main(){ >> stringstream ss; >> return 0; >> } >> >> Why does the above cause this 'bug'? > > Trying... > > $ valgrind --version > valgrind-3.4.1-Debian > $ g++ --version > g++ (Debian 4.3.3-3) 4.3.3 > $ valgrind ./a.out > ... > ==2990== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 17 from 1) > ==2990== malloc/free: in use at exit: 0 bytes in 0 blocks. > ==2990== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. > ==2990== For counts of detected errors, rerun with: -v > ==2990== All heap blocks were freed -- no leaks are possible. > ... > > Which versions are you using? Is your C++ lib in good shape?
I don't get the error either, with the same Valgrind version on my Ubuntu 9.04 box. Judging from the stack trace, it's a bug in the libc which you probably can't do much about. I'd suppress it -- use --gen-suppressions=yes to do so. Nick ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
