Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Content-class: urn:content-classes:message Subject: Re: maintaining bash MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 8 Apr 2005 15:06:02 +0200 Message-ID: <79F81D5F4790D344B05F489CE2AC8AB717CEFD@dubexdc03.dubex.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "David Dindorp" To: X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j38D6dsV020715 Corinna Vinschen wrote: > On Apr 8 12:19, David Dindorp wrote: >> To be fair, this is probably more a Cygwin DLL problem than a bash >> problem, or perhaps a "bash hasn't kept up with changes in Cygwin >> because the maintainer haven't had the time" problem. It's running >> quite stable under 1.5.10, it sucks with 1.5.12 and 1.5.13 and any >> of the latest snapshots.. (Haven't tried 1.5.11, but I will as soon >> as I get the time.) > > It would be more helpful to test with 1.5.14 and current snapshots > and to help tracking down the problem in Cygwin you suspect. I'd love to. Actually I've tried ~10 different recent snapshots in a couple of the test environments that we have here, and they all worked pretty bad. The snapshots have a tendency to cause bash to crash rather than hang, which means I haven't got more than a stack trace to go by. I've posted some of them to this list, but haven't really got any pointers to what could be wrong in any of the cases. Since I don't know Cygwin that well, I'm having a hard time figuring it out myself. I thought I'd spare the list the noise of reposting the traces, and so I'm basically just stuck. If you can tell me how to proceed from here, I'd be happy to throw in a bunch of manhours to try and find out what's wrong. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/