tags 674917 + upstream patch
quit
Hi,
Antti-Juhani Kaijanaho wrote:
However, so far as I can see, ignoring the return value of mblen is never a
security problem and is sometimes appropriate (the first call to the function
is often mblen(NULL, 0), the result value of which is usually of no
On Tue, May 29, 2012 at 11:36:03AM -0500, Jonathan Nieder wrote:
This doesn't seem to be fixed upstream, so please report it to
http://sourceware.org/bugzilla, product glibc, component libc and
let us know the bug number so we can track it.
It is commonly accepted Debian practice for the
forwarded 674917 http://sourceware.org/PR14176
quit
Antti-Juhani Kaijanaho wrote:
However, I've done what you asked.
http://sourceware.org/bugzilla/show_bug.cgi?id=14176
Thanks much.
Kind regards,
Jonathan
--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject
Package: libc6-dev
Version: 2.13-32
Severity: normal
GCC documentation states:
The warn_unused_result attribute causes a warning to be emitted if a caller
of the function with this attribute does not use its return value. This is
useful for functions where not checking the result is either
4 matches
Mail list logo
