[EMAIL PROTECTED] wrote:
Configuration Information [Automatically generated, do not change]: Machine: alpha OS: netbsd Compiler: cc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='alpha' -DCONF_OSTYPE='netbsd' -DCONF_MACHTYPE='alpha--netbsd' -DCONF_VENDOR='' -DLOCALEDIR='/usr/pkg/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -DDEFAULT_PATH_VALUE=/usr/bin:/bin:/usr/pkg/bin:/usr/local/bin -I/usr/include -O2 -mieee -I/usr/include uname output: NetBSD faeroes 3.1.1_PATCH NetBSD 3.1.1_PATCH (sdf) #0: Mon Jul 2 15:57:43 UTC 2007 [EMAIL PROTECTED]:/var/netbsd/arch/alpha/compile/sdf alpha Machine Type: alpha--netbsdBash Version: 3.2 Patch Level: 33 Release Status: release Description: On newer versions of NetBSD (seemingly anything v.3 or above), attempts to use any of the wildcards '*', '?', and '[' ... ']' (though not '{' ... '}') result in bash suddenly terminating & creating a core image, having received "signal 12." This happens regardless of the number of matches and regardless of whether there are any matches at all. Interestingly, if the 'failglob' option is set, bash prints a message about being unable to find any matches (even if there were matches) before terminating. This bug has only been observed in the version of bash specified above.
Sorry, I can't reproduce this on any of my systems. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRU [EMAIL PROTECTED] http://cnswww.cns.cwru.edu/~chet/
