Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale'
-DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -DDEBUG -DMALLOC_DEBUG -I. -I.
-I./include -I./lib -g -O2
uname output: Linux imbroglio 2.6.18-92.1.13.el5PAE #1 SMP Thu Sep 4
04:05:54 EDT 2008 i686 i686 i386 GNU/Linux
Machine Type: i686-pc-linux-gnu
Bash Version: 3.2
Patch Level: 0
Release Status: dev
Description:
I have a large system building with make that eventually falls over
when bash crashes with a segmentation fault. Looking closer, after
cd'ing to a directory created during the make, any non-built-in command
crashes. I ran a debug build of bash to try to capture a stack trace for
this report but there were no symbols in the core file. Running in gdb
it looks like the crash occurs after forking the child process and the
core probably comes from the command, not bash. Built-in commands do not
crash. If you cd out of this directory, non-built-ins start working
again. There's something about this directory that bash doesn't like. It
was created in the usual way by mkdir during the execution of make.
Repeat-By:
cd to suspect directory and execute non-built-in command like 'ls' and
it crashes with segmentation fault. Built-in command like 'pwd'works. cd
out of the evil directory and non-built-in commands work.
