Indeed, with build from devel it doesn't segfault anymore. Just out of pure curiosity, which commit introduced a fix for that? Aaand, there's one more thing that puzzles me a bit:
# echo $BASH_VERSION 5.0.12(1)-alpha # echo ${LANG:-bleh} bleh # LANG=UTF-8 # printf '%s\n' $'\u013b' Ļ # unset LANG # : # \o/ no segfaults # printf '%s\n' $'\u013b' \u013B # LANG=UTF-8 # printf '%s\n' $'\u013b' \u013B # why it returns just the code? bash-5.0# When LANG is set to UTF-8, printf returns actual character which coresponds to given code after first call, however, after LANG is toggled, printf keeps returning just the code. I guess my question here is: why that happens? I mean, I would expect it to decode it whenever LANG is set back to UTF-8 in this case. Am I missing something here? 2018-02-09 17:29 GMT+01:00 Chet Ramey <chet.ra...@case.edu>: > On 2/9/18 11:21 AM, mike b wrote: > > Core was generated by `bash'. > > Program terminated with signal SIGSEGV, Segmentation fault. > > #0 __gconv_close (cd=0x0) at gconv_close.c:35 > > 35 gconv_close.c: No such file or directory. > > (gdb) bt > > #0 __gconv_close (cd=0x0) at gconv_close.c:35 > > #1 0x00007fbf1e17a59f in iconv_close (cd=<optimized out>) at > iconv_close.c:35 > > #2 0x00000000004964d0 in u32reset () > > #3 0x000000000046de67 in ?? () > > #4 0x000000000043b403 in sv_locale () > > #5 0x000000000043e53d in makunbound () > > #6 0x0000000000481d45 in unset_builtin () > > #7 0x00000000004327aa in ?? () > > #8 0x00000000004349d4 in ?? () > > #9 0x0000000000435b1b in execute_command_internal () > > #10 0x000000000043737e in execute_command () > > #11 0x00000000004213be in reader_loop () > > #12 0x000000000041fca5 in main () > > (gdb) > > Thanks. I'm pretty sure this is the problem I fixed last November. The fix > is in the devel branch if you want to try that. > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/ >