diff options
author | Carlos O'Donell <carlos@redhat.com> | 2020-01-08 13:24:42 -0500 |
---|---|---|
committer | Carlos O'Donell <carlos@redhat.com> | 2020-04-26 13:55:58 -0400 |
commit | 92954ffa5a5662fbfde14febd7e5dcc358c85470 (patch) | |
tree | ea7eb81874f0b3d706e701eda47f29718f7d948f /nptl/tst-eintr2.c | |
parent | 8d9ffbb9d00669f62d5ddb4283b7c3d03955d942 (diff) | |
download | glibc-92954ffa5a5662fbfde14febd7e5dcc358c85470.zip glibc-92954ffa5a5662fbfde14febd7e5dcc358c85470.tar.gz glibc-92954ffa5a5662fbfde14febd7e5dcc358c85470.tar.bz2 |
localedef: Add verbose messages for failure paths.
During testing of localedef running in a minimal container
there were several error cases which were hard to diagnose
since they appeared as strerror (errno) values printed by the
higher level functions. This change adds three new verbose
messages for potential failure paths. The new messages give
the user the opportunity to use -v and display additional
information about why localedef might be failing. I found
these messages useful myself while writing a localedef
container test for --no-hard-links.
Since the changes cleanup the code that handle codeset
normalization we add tst-localedef-path-norm which contains
many sub-tests to verify the correct expected normalization of
codeset strings both when installing to default paths (the
only time normalization is enabled) and installing to absolute
paths. During the refactoring I created at least one
buffer-overflow which valgrind caught, but these tests did not
catch because the exec in the container had a very clean heap
with zero-initialized memory. However, between valgrind and
the tests the results are clean.
The new tst-localedef-path-norm passes without regression on
x86_64.
Change-Id: I28b9f680711ff00252a2cb15625b774cc58ecb9d
Diffstat (limited to 'nptl/tst-eintr2.c')
0 files changed, 0 insertions, 0 deletions