Re: Unexpected (?) segfault after unset LANG

[mike b]

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)


2018-02-09 16:21 GMT+01:00 Chet Ramey <chet.ramey@case.edu>:

> On 2/9/18 9:55 AM, mike b wrote:
>
> > Bash Version: 4.3
> > Patch Level: 33
> > Release Status: release
> >
> > Description:
> > On the system which doesn't provide any locale (other than default, POSIX
> > one), Bash is hit with a segfault after the following is executed (I fork
> > into another Bash instance so the error about the segfault is clearly
> > visible):
>
> Stack traceback? The common element in all of these appears to be $'...'.
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/
>