Bug 19052 - While running testsuite on Windows xp, I think I found failure of printf/sprintf %e format.
Summary: While running testsuite on Windows xp, I think I found failure of printf/spri...
Status: RESOLVED FIXED
Alias: None
Product: gdb
Classification: Unclassified
Component: testsuite (show other bugs)
Version: 7.10
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
: 19053 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-10-02 02:17 UTC by YongHao Hu
Modified: 2015-11-03 09:04 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments
the log of error (679 bytes, text/plain)
2015-10-02 02:17 UTC, YongHao Hu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description YongHao Hu 2015-10-02 02:17:36 UTC
Created attachment 8670 [details]
the log of error

https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-gdb/PKGBUILD

The error was:
out: demangle.test!(1.17549e-038)
exp: demangle.test!(1.17549e-38)

We can reproduce this bug using
#include <stdio.h>
int main()
{
    double x = 3.40282e+038;
    printf("%.5e", x);
}

I don't know whether this was testsuite's problem or implementation of gdb.
I will try to fix it when I know the expect result of gdb.
Thank you.
Comment 1 Pedro Alves 2015-11-02 20:34:57 UTC
The failures in question are:

~~~
./test-demangle < ../../../gdb-7.10/libiberty/testsuite/d-demangle-expected
FAIL at line 750, options --format=dlang:
in:  _D8demangle23__T4testVfe0FFFFFFP128Zv
out: demangle.test!(3.40282e+038)
exp: demangle.test!(3.40282e+38)
FAIL at line 758, options --format=dlang:
in:  _D8demangle19__T4testVfe08PN125Zv
out: demangle.test!(1.17549e-038)
exp: demangle.test!(1.17549e-38)
E:\MINGW-packages\mingw-w64-gdb\src\build-i686-w64-mingw32\libiberty\testsuite\test-demangle.exe: 266 tests, 2 failures
~~~
Comment 2 Qian Hong 2015-11-03 09:02:52 UTC
Tested with latest git source, confirming fixed by 30379291886a171e6dc202122bc1c583318c2e17

Thanks Pedro and Iain!
Comment 3 Qian Hong 2015-11-03 09:04:10 UTC
*** Bug 19053 has been marked as a duplicate of this bug. ***