On Tue, Jul 4, 2017 at 8:13 PM, Martijn Dekker <[email protected]> wrote: > Op 04-07-17 om 19:51 schreef Denys Vlasenko: >> You said earlier that environment makes no difference. > > That was incorrect, sorry about that. > >> For the locale, >> it should make a difference. Can you confirm that after setting >> all LC_foo variables to "C" bug does not trigger? > > Yes, I can confirm that. > > In fact, setting just LC_ALL to C, or any non-UTF-8 locale, is > apparently sufficient to stop the bug from being triggered (which makes > sense, as setting LC_ALL is supposed to cause all other LC_* variables > to be ignored).
Ok. I just tested it again, and it works for me. Let's narrow it down more. My libc is: $ /lib64/libc.so.6 GNU C Library (GNU libc) development release version 2.25.90, by Roland McGrath et al. Copyright (C) 2017 Free Software Foundation, Inc. $ rpm -qa | grep glibc glibc-headers-2.25.90-1.fc27.x86_64 glibc-static-2.25.90-1.fc27.i686 glibc-2.25.90-1.fc27.x86_64 ... Yours? Does the bug happen with the current git? (I ask this because this would mean I don't need to go to 1.25.0 every time I want to try reproducing it again). _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
