Description of problem: Glibc fails to parse 0 in scientific notation. This breaks the ATLAS build system, failing with a segfault in RunMADef (atlas-3.8.4) or an assertion failure in RunMulAdd (atlas-3.10.1). Version-Release number of selected component (if applicable): * Fedora 20 * glibc-devel-2.18-11.fc20 How reproducible: Always. Steps to Reproduce: $ cat test.c #include <stdio.h> int main() { float a, b; int r = sscanf("0e+0 42", "%f %f", &a, &b); printf("r=%d a=%f b=%f\n", r, a, b); return 0; } Actual results: $ gcc test.c && ./a.out r=1 a=0.000000 b=0.000000 Expected results: r=2 a=0.000000 b=42.000000 Additional info: * https://sourceware.org/bugzilla/show_bug.cgi?id=15917
Volker, Thanks. Sorry about this. We'll get this fixed ASAP. Siddhesh, Would you mind looking at the backport?
glibc-2.18-12.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/glibc-2.18-12.fc20
Package glibc-2.18-12.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.18-12.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-1830/glibc-2.18-12.fc20 then log in and leave karma (feedback).
glibc-2.18-12.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.