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 22:54:55 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin bughunt (FAQ alert?)
Message-ID: <20050122035454.GA25952@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <D9B1ABFA3404D611AC7B00508B63B512024F106E AT nnhml1 DOT cox DOT co DOT uk> <20050121121553 DOT GQ3113 AT cygbert DOT vinschen DOT de> <20050121163843 DOT GE20002 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT GSO DOT 4 DOT 61 DOT 0501211146420 DOT 18105 AT slinky DOT cs DOT nyu DOT edu> <20050121190233 DOT GD20866 AT trixie DOT casa DOT cgf DOT cx> <20050121194544 DOT GA138715 AT Worldnet> <20050121194720 DOT GF20866 AT trixie DOT casa DOT cgf DOT cx> <20050121222838 DOT GA141219 AT Worldnet>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050121222838.GA141219@Worldnet>
User-Agent: Mutt/1.4.1i

On Fri, Jan 21, 2005 at 05:28:38PM -0500, Pierre A. Humblet wrote:
>On Fri, Jan 21, 2005 at 02:47:20PM -0500, Christopher Faylor wrote:
>>On Fri, Jan 21, 2005 at 02:45:44PM -0500, Pierre A. Humblet wrote:
>>>On Fri, Jan 21, 2005 at 02:02:33PM -0500, Christopher Faylor wrote:
>>>> 
>>>>   tar xjf cygwin-1.5.12-1-src.tar.bz2
>>>>   cd cygwin-1.5.12-1
>>>>   mkdir build
>>>>   cd build
>>>>   (../configure; make) >& make.out
>>>> 
>>>>It does make sense to check CVS or a snapshot to see if your problem is
>>>>fixed before you go to any effort trying to debug a problem, however.
>>>
>>>Great.  Just put the above in the FAQ, plus some words about needing an
>>>unstripped dll.
>>
>>Information about building the DLL is already in the FAQ.
>
>If you refer to http://cygwin.com/faq/faq0.html#SEC102 it has the
>apparently obsolete information about needing a separate w32api and it
>recommends to use cvs.

You included the section where I said it was probably a good idea to use
CVS or a snapshot.  So, the FAQ is accurate there.  You're right that
the rest of it should be updated.

However, if the fact that the cygwin FAQ entry is mildly inaccurate was
a true stumbling block for people who wanted to debug the DLL, then I
think we would have seen a complaint about it by now.

I think it's pretty clear that the people who are clamoring for this
don't really know what they want and assume that a dll with debugging
symbols will either enable them to debug the dll without going through
the awful rigors of building or they think they would have a better
opportunity of having cygwin tech support look at their back traces.
Neither is precisely true.

However, I have already said that it is on my todo list to try to
provide a debuginfo package for cygwin.  It will show up in some
future release.

cgf

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