X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_54,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Message-ID: <4A4D4BA8.8090202@byu.net> Date: Thu, 02 Jul 2009 18:07:04 -0600 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] [1.7] Updated [security]: bash-3.2.49-23 and Windows 7 RC References: <4A4D200E DOT 9050401 AT sidefx DOT com> <4A4D2342 DOT 6050400 AT sidefx DOT com> In-Reply-To: <4A4D2342.6050400@sidefx.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com -----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 libreadline6. Yes, a side effect of the version bump is a library dependency change, so setup.hint no longer explicitly lists 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 worthwhile confirming on it. I don't have access to any of these (just XP, here), so I can't really tell where things are crashing. It works just fine for me. > Frame Function Args > 0028CCE8 04FF0000 (6120B808, 6120C41C, 0028CD50, 61020360) > 0028CD78 61020293 (00000000, 0028CDB0, 610066C0, 7EFDE000) 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. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpNS6gACgkQ84KuGfSFAYDcGQCeN6jGHQ5tEuepsIAudxFrxcpg 00oAoMZhUO01XKJ0m+7WW656HP8s/SOV =Ku9F -----END PGP SIGNATURE----- -- 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