Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 21 Jan 2005 10:45:48 -0500
From: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin bughunt (FAQ alert?)
Message-ID: <20050121154548.GA533675@Worldnet>
References: <79F81D5F4790D344B05F489CE2AC8AB7109544 AT dubexdc03 DOT dubex DOT net> <20050120200455 DOT GK9369 AT trixie DOT casa DOT cgf DOT cx> <cb51e2e05012012475c668d43 AT mail DOT gmail DOT com> <20050120220004 DOT GA67407 AT Worldnet> <20050121114439 DOT GN3113 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050121114439.GN3113@cygbert.vinschen.de>
User-Agent: Mutt/1.4.1i

On Fri, Jan 21, 2005 at 12:44:39PM +0100, Corinna Vinschen wrote:
> On Jan 20 17:00, Pierre A. Humblet wrote:
> > 
> > This must be modulated by the warnings on the snapshot page,
> > so I would recommend an initial step: write to the list, describe
> > the bug and ask for a recommended snapshot.
> > Should we also provide an optional cygwin_debug package, with only
> > an unstripped cygwin1.dll.debug ?
> 
> I don't think so.  I don't recall that any Linux distro contains a
> debug-enabled kernel.  I guess, those who feel confident to debug the
> kernel (here: the Cygwin DLL), should be able to build their own
> debug version.

Except that Cygwin changes at a high rate. Debugging a transient 
problem that shows up on 1.5.12 with the current cvs is taking a gamble.
There is a high probability you will first stumble on another bug.

If you have a debug dll, you can debug from a dump, or use the debug
dll in a production environment with just in time debugging enabled.
Once the bug is found, you may conclude it's gone from cvs, but that's
a firm (and satisfactory) conclusion. On the other hand if you can't
reproduce the bug with cvs, you don't know if it's really gone ot if
its likelihood is just reduced.

Pierre

--
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/