Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Tue, 27 Jan 2004 09:50:00 -0600 (CST) From: Brian Ford X-X-Sender: ford@eos To: David Rothenberger cc: cygwin@cygwin.com Subject: Re: ash signal problems with latest CVS In-Reply-To: <4015B3ED.1060604@acm.org> Message-ID: References: <16405.41671.479106.886434@forbin.entomo.com> <4015B3ED.1060604@acm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Reply-To: cygwin@cygwin.com On Mon, 26 Jan 2004, David Rothenberger wrote: > Brian Ford wrote: > > Are you sure this is the latest CVS? It looks like the same problem fixed > > here to me: > > > > http://www.cygwin.com/ml/cygwin/2004-01/msg01140.html > > > Yes, I'm sure it is the latest CVS. The problem above is fixed in my > build, but not the problem I reported. It looks the same, but the shells > are different... > Sorry. I should have tried to reproduce it before replying. Incidentally, is there a way to reliably compare two CVS built DLLs from the cygcheck or uname -a output? FWIW, this problem appears to be fixed by: http://www.cygwin.com/ml/cygwin/2004-01/msg01160.html -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- 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/