Package: libstdc++6 Version: 4.3.2-1.1 Severity: important http://etbe.coker.com.au/2009/06/22/valgrindhelgrind-and-stl-string http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40518
The above GCC bug report which was created by Jonathan Wakely after reading my blog concerns a case where calling empty() on an empty string will be regarded as not being thread-safe by helgrind. I am not sure if this is a real problem (IE something that can corrupt memory) or whether it's a cosmetic error (something that just causes helgrind warnings). Due to this being the main error that helgrind flags on a program that later has an assertion from free() I suspect that it may actually corrupt memory. But if however it happens to not corrupt memory I still think that it is important enough to justify an update to Lenny to fix this. Allowing debugging tools such as helgrind to work to their maximum potential is quite important to improve the overall quality of the code. I have reproduced this bug in version 4.3.3-12 in Unstable. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash Versions of packages libstdc++6 depends on: ii gcc-4.3-base 4.3.2-1.1 The GNU Compiler Collection (base ii libc6 2.7-18 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1.1 GCC support library libstdc++6 recommends no packages. libstdc++6 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
