[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#534193: marked as done (libstdc++6: calling erase() on a new empty string will cause a helgrind error report)

Your message dated Tue, 22 Jun 2010 14:33:27 +0200
with message-id <4C20AD97.5080503@debian.org>
and subject line Re: Bug#534193: libstdc++6: calling erase() on a new empty string will cause a helgrind error report
has caused the Debian Bug report #534193,
regarding libstdc++6: calling erase() on a new empty string will cause a helgrind error report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
534193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534193
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
Version: 4.4.4-1

On 22.06.2009 13:59, Russell Coker wrote:

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.

--- End Message ---
Reply to: