On Sun, Jul 2, 2017 at 2:36 PM, Martijn Dekker <[email protected]> wrote: >>>> Let's find out why it doesn't work for you. Is it environment? >>> [...] >>> >>> Nope, environment makes no difference. >>> >>> Finally found the time to track down the bug on my machine. It is >>> triggered by CONFIG_LOCALE_SUPPORT. Disabling that option makes the bug >>> go away reliably. (I also noticed this option is not enabled by default.) >> >> Well, this is good that it was narrowed, but LOCALE_SUPPORT >> is expected to work, no breakage in ash should result. >> IOW: it is most likely a bug. > > Indeed. > >> What LANG / LC_ALL / other locale env setup this is happening on? > > On any UTF-8 locale, regardless of country or language setting. > > For instance, on mine: > $ locale > LANG=nl_NL.UTF-8 > LC_CTYPE="nl_NL.UTF-8" > LC_NUMERIC="nl_NL.UTF-8" > LC_TIME="nl_NL.UTF-8" > LC_COLLATE=C > LC_MONETARY="nl_NL.UTF-8" > LC_MESSAGES="nl_NL.UTF-8" > LC_PAPER="nl_NL.UTF-8" > LC_NAME="nl_NL.UTF-8" > LC_ADDRESS="nl_NL.UTF-8" > LC_TELEPHONE="nl_NL.UTF-8" > LC_MEASUREMENT="nl_NL.UTF-8" > LC_IDENTIFICATION="nl_NL.UTF-8" > LC_ALL= > > ...but also on en_US.UTF-8, fr_FR.UTF-8, etc.
You said earlier that environment makes no difference. For the locale, it should make a difference. Can you confirm that after setting all LC_foo variables to "C" bug does not trigger? _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
