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
There's no call to memcpy in setifs(), and the line numbers are off. Are you sure this is bash3 patch 16?
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU [EMAIL PROTECTED] http://cnswww.cns.cwru.edu/~chet/
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
