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.
--
Antti-Juhani Kaijanaho
Attachment:
signature.asc
Description: Digital signature