Your message dated Wed, 16 Nov 2016 15:08:02 +0100
with message-id <4bc5ecd2-0a76-6c26-8b9d-7406cfefd...@debian.org>
and subject line Re: [PR libstdc++/21334] race condition in libstdc++3
(basic_string.tcc)
has caused the Debian Bug report #140201,
regarding [PR libstdc++/21334] race condition in libstdc++3 (basic_string.tcc)
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 ow...@bugs.debian.org
immediately.)
--
140201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=140201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++3
Version: 1:3.0.3-1
Severity: normal
The function basic_string::_M_leak_hard() in basic_string.tcc is not
thread-safe. The reference count is read with _M_is_shared() and
then written with _M_set_leaked(), non-atomically. (This is only a
bug if the string class is supposed to be thread-safe. I haven't found
an explicit statement that it is, but most of the string operations
are written to be thread-safe.)
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux galaxy 2.4.14-pre6 #1 Thu Nov 1 02:23:35 PST 2001 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages libstdc++3 depends on:
ii gcc-3.0-base 1:3.0.3-1 The GNU Compiler Collection (base
ii libc6 2.2.5-3 GNU C Library: Shared libraries an
ii libgcc1 1:3.0.3-1 GCC support library.
--- End Message ---
--- Begin Message ---
Version: 5.1.0-1
according to upstream:
"This is no longer an issue when using the new non-reference-counted std::string
implementation in GCC 5."
--- End Message ---
