Hi Bruno,
On 4/26/24 10:51 PM, Bruno Haible wrote:
> welcome to the daily business of Gnulib test failures and workarounds!
Thanks for the welcome!
I would have worked a bit harder and tried to come up with a patch,
but I am not very familiar with the wide character and multibyte
string functions (wcrtomb is mentioned in the comment). I guess only
knowing English made me lazy. :)
> Does the test failure persist when the tests are compiled with "-ggdb"
> instead of "-g -O2"? (Change CFLAGS in gltests/Makefile.)
Interesting. Using "-ggdb" in gltests/Makefile fixes both failures.
I'm assuming that -O2 is the important change here? I know very little
about GCC's optimizations so feel free to educate me.
> Does the test program use rpl_sprintf defined by Gnulib, or does it use
> sprintf from glibc directly? (Use 'nm test-sprintf | grep printf'.) In
> the first case, does the test failure persist when the Gnulib replacement
> code is compiled with "-ggdb" instead of "-g -O2"? (Change CFLAGS in
> gllib/Makefile.)
Both use them from glibc directly. I feel a bit silly for not checking
that before...
$ nm gltests/test-sprintf-posix | grep 'printf'
U fprintf@GLIBC_2.2.5
U sprintf@GLIBC_2.2.5
$ nm gltests/test-snprintf-posix | grep 'printf'
U fprintf@GLIBC_2.2.5
U snprintf@GLIBC_2.2.5
Collin
