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

Bug#674917: marked as done (libc6-dev: mblen is erroneously marked warn_unused_result)

Your message dated Wed, 28 May 2014 22:29:54 +0200
with message-id <20140528202954.GA23103@volta.rr44.fr>
and subject line Re: libc6-dev: mblen is erroneously marked warn_unused_result
has caused the Debian Bug report #674917,
regarding libc6-dev: mblen is erroneously marked warn_unused_result
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.)


-- 
674917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674917
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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 a security
  problem or always a bug, such as realloc.

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 interest).

(Debian's use of -D_FORTIFY_SOURCE=2 and the common policy of using -Werror
together make this a noncosmetic issue.)

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4.0-ibid-1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libc6-dev depends on:
ii  libc-dev-bin    2.13-32
ii  libc6           2.13-32
ii  linux-libc-dev  3.2.18-1

Versions of packages libc6-dev recommends:
ii  gcc [c-compiler]      4:4.7.0-6
ii  gcc-4.4 [c-compiler]  4.4.7-1
ii  gcc-4.5 [c-compiler]  4.5.3-12
ii  gcc-4.6 [c-compiler]  4.6.3-5
ii  gcc-4.7 [c-compiler]  4.7.0-9

Versions of packages libc6-dev suggests:
ii  glibc-doc     <none>
ii  manpages-dev  3.40-0.1

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.18-1

On Mon, May 28, 2012 at 06:55:16PM +0300, Antti-Juhani Kaijanaho wrote:
> 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 a security
>   problem or always a bug, such as realloc.
> 
> 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 interest).
> 
> (Debian's use of -D_FORTIFY_SOURCE=2 and the common policy of using -Werror
> together make this a noncosmetic issue.)
> 

This bug has been fixed in version 2.18-1. Closing the bug accordingly.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: