[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: 'case' UTF-8 bug
From:       Denys Vlasenko <vda.linux () googlemail ! com>
Date:       2017-02-01 12:27:59
Message-ID: CAK1hOcNFwTsoiTah7P+QoaKDt8PKwg59R5YWWrTugsooqJJ_WQ () mail ! gmail ! com
[Download RAW message or body]

On Sat, Dec 24, 2016 at 2:17 PM, Martijn Dekker <martijn@inlv.org> wrote:
> Op 24-11-16 om 08:22 schreef Denys Vlasenko:
>> On Thu, Nov 24, 2016 at 2:57 AM, Martijn Dekker <martijn@inlv.org> wrote:
>>> Op 24-11-16 om 00:14 schreef Denys Vlasenko:
>>>> Can't reproduce:
>>> [...]
>>>> Tried with CONFIG_FEATURE_SH_STANDALONE=y and it still works for me.
>>>>
>>>> Please send your .config
>>>
>>> OK, see attached.
>>
>> Still can't reproduce, 1.25.1 works fine with your config
>> on my machine.
>>
>> 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.

What LANG / LC_ALL / other locale env setup this is happening on?
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]