[ANNOUNCEMENT] [1.7] Updated [security]: bash-3.2.49-23 and Windows 7 RC

[Edward Lam]

Eric Blake wrote:
> 61020293 looks like an address in the dll range, probably cygwin1.dll.  It
> would be nice to know what function is dying, but doing that may require
> rebuilding a bash image with debugging symbols.  Did you by chance do any
> rebasing?  Maybe this is a case where I didn't use the correct gcc-4 flags
> for compilation, at which point an updated binutils/gcc might fix things.

No, I didn't do any rebasing. I also tried using rebaseall and 
peflagsall to no avail.

Incidentally, is installing the bash and libreadline source broken? If I 
install the src for say, the make package, it installs it into a 
subdirectory under /usr/src. But when I tried to do the same for 
bash-3.2.49-23, I just got a bash src tar ball along with a bunch of 
patch files. Is this expected?

-Edward

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple