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

Ok, so I can confirm a problem with bash 3.2.49-23 on Windows 7 RC build 7100 64-bit. Basically, bash just crashes on startup. I don't have access to a Vista machine right now but it's worthwhile confirming on it. I don't have access to any of these (just XP, here), so I can't really tell

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

On Jul 3 10:11, Vincent R. wrote: Ok, so I can confirm a problem with bash 3.2.49-23 on Windows 7 RC build 7100 64-bit. Basically, bash just crashes on startup. I don't have access to a Vista machine right now but it's worthwhile confirming on it. I don't have access to any of these

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

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

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

Edward Lam edward at sidefx.com writes: 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

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

On Fri, 3 Jul 2009 14:03:35 + (UTC), Eric Blake e...@byu.net wrote: Edward Lam edward at sidefx.com writes: 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

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

Vincent R. forumer at smartmobili.com writes: is it the first time you compile readline with gcc-4 ? Yes, plus readline 6.0 is a new upstream release. -- Eric Blake -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

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

Dave Korn dave.korn.cygwin at googlemail.com writes: I'm wondering if the problem is not how I compiled bash, but how I compiled readline. Dave, any pointers I should try or maybe a missed compiler flag I should have used to build libreadline7 with gcc4? I'm shooting in the dark,

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

Eric Blake wrote: Dave Korn dave.korn.cygwin at googlemail.com writes: I'm wondering if the problem is not how I compiled bash, but how I compiled readline. Dave, any pointers I should try or maybe a missed compiler flag I should have used to build libreadline7 with gcc4? I'm shooting

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

Eric Blake wrote: I'm wondering if the problem is not how I compiled bash, but how I compiled readline. Dave, any pointers I should try or maybe a missed compiler flag I should have used to build libreadline7 with gcc4? I'm shooting in the dark, since I can't seem to reproduce the

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

Hi Eric, I got bash 3.2.49-22 running again in cygwin 1.7 after explicitly installing libreadline6. Ok, so I can confirm a problem with bash 3.2.49-23 on Windows 7 RC build 7100 64-bit. Basically, bash just crashes on startup. I don't have access to a Vista machine right now but it's

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please don't top-post, and trim your replies to just include relevant text: http://cygwin.com/acronyms/#TOFU According to Edward Lam on 7/2/2009 3:14 PM: Hi Eric, I got bash 3.2.49-22 running again in cygwin 1.7 after explicitly installing