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

Bug#155835: marked as done (libc6-dev: scanf a flag conflicts with C99)

Your message dated Sat, 11 Apr 2015 11:47:11 +0200
with message-id <20150411094711.GC3909@aurel32.net>
and subject line Re: Bug#155835: libc6-dev: scanf a flag conflicts with C99
has caused the Debian Bug report #155835,
regarding libc6-dev: scanf a flag conflicts with C99
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.)


-- 
155835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=155835
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6-dev
Version: 2.2.5-12
Severity: normal
Tags: upstream

The "a" flag to scanf (a GNU extension, used like %as) conflicts with
the C99 definition of the a conversion.  GCC 3 already warns about the
use of %a with -std=c99 and -std=gnu99, but the libc version uses the
GNU semantics.  This should be fixed eventually.  In the meantime, the
documentation should be changed to warn about this.

>From ISO/IEC 9899:1999 (E), page 278:

   a,A    A double argument representing a floating-point number [...]

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux kukkaruukku 2.4.18-686 #1 Sun Apr 14 11:32:47 EST 2002 i686
Locale: LANG=fi_FI@euro, LC_CTYPE=fi_FI@euro

Versions of packages libc6-dev depends on:
ii  libc6                         2.2.5-12   GNU C Library: Shared libraries an

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.7-1

On 2015-03-29 12:24, Antti-Juhani Kaijanaho wrote:
> On Sat, Mar 28, 2015 at 07:46:37PM +0000, Jean-Michel Nirgal Vourgère wrote:
> > I suppose it has been fixed.
> > scanf(3) now includes a note about specific '%a' behaviour when -std=c99
> > is used.
> 
> Yes, it looks like it's fixed (though your attached log does not show it); I
> cannot reproduce the issue either.
> 
> Also, there's a long change log entry in
> /usr/share/doc/glibc-doc/ChangeLog.17.gz indicating changes that likely fixed
> this:
> 
> 2007-09-17  Jakub Jelinek  <jakub@redhat.com>
> 
>         * include/stdio.h (__isoc99_fscanf, __isoc99_scanf,
>         __isoc99_sscanf, __isoc99_vscanf): New prototypes.
>         (__isoc99_vsscanf, __isoc99_vfscanf): New prototypes, add
>         libc_hidden_proto.
>         * include/wchar.h (__isoc99_fwscanf, __isoc99_wscanf,
>         __isoc99_swscanf, __isoc99_vwscanf): New prototypes.
>         (__isoc99_vswscanf, __isoc99_vfwscanf): New prototypes,
>         add libc_hidden_proto.
>         * libio/stdio.h (fscanf, scanf, sscanf, vfscanf, vscanf,
>         vsscanf): Redirect to __isoc99_* if strict ISO C99 or POSIX
>         conformance requested.
> 
> [...]
> 
> > Can we now close this bug?
> 
> It looks like it can be closed.  If you can figure out what version the above
> changelog entry attaches to, you can also deduce an appropriate fixed version.

Thanks for digging into this bug. According to my findings, it has been
fixed in version glibc version 2.7. I am therefore closing this bug with
version 2.7-1.

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

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: