Chet Ramey writes:
> Matthias Klose wrote:
> > The command
> >
> > IFS="$(echo -e "\255")"
> >
> > (which is found in the burncdda shell script)
> > causes a seg fault. The same command does not have a problem in version
> > 2.05b-24
>
> I can't reproduce this with bash-3.0 (all released patches) on
> MacOS X, FreeBSD, or Red Hat 8. A stack traceback would be
> helpful.
(gdb) run
Starting program: /home/packages/bash/bash-3.0/build-bash/bash
[EMAIL PROTECTED]:/home/packages/bash/bash-3.0/build-bash$ IFS="$(echo -e
"\255")"
Program received signal SIGSEGV, Segmentation fault.
0x41092dec in memcpy () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt
#0 0x41092dec in memcpy () from /lib/tls/i686/cmov/libc.so.6
#1 0x080867d0 in setifs (v=0x8102208) at ../bash/subst.c:6955
#2 0x0807455c in stupidly_hack_special_variables (name=0x8102208 "")
at ../bash/variables.c:3738
#3 0x0807f0aa in do_assignment_internal (string=0x80f7d88 "ßßßßßßßß\b",
expand=1) at ../bash/subst.c:2191
#4 0x0807f30a in do_assignment (string=0x8102208 "") at ../bash/subst.c:2206
#5 0x0808714e in expand_word_list_internal (list=0x80f29a8, eflags=135248744)
at ../bash/subst.c:7460
#6 0x080869aa in expand_words (list=0x8102208) at ../bash/subst.c:7150
#7 0x0806d9bd in execute_simple_command (simple_command=0x8102108,
pipe_in=-1, pipe_out=-1, async=0, fds_to_close=0x8102128)
at ../bash/execute_cmd.c:2793
#8 0x0806a988 in execute_command_internal (command=0x8101fa8, asynchronous=0,
pipe_in=-1, pipe_out=-1, fds_to_close=0x8102128)
at ../bash/execute_cmd.c:660
#9 0x0806a4b5 in execute_command (command=0x8102208)
at ../bash/execute_cmd.c:347
#10 0x0805dd80 in reader_loop () at ../bash/eval.c:146
#11 0x0805bb46 in main (argc=1, argv=0xbffff994, env=0xbffff99c)
at ../bash/shell.c:704
(gdb)
