Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Fri, 21 Jan 2005 11:31:28 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin bughunt (more FAQ stuff)
Message-ID: <20050121163128.GC20002@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <79F81D5F4790D344B05F489CE2AC8AB7109577 AT dubexdc03 DOT dubex DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <79F81D5F4790D344B05F489CE2AC8AB7109577@dubexdc03.dubex.net>
User-Agent: Mutt/1.4.1i

On Fri, Jan 21, 2005 at 10:47:20AM +0100, David Dindorp wrote:
>Joshua Daniel Franklin wrote:
>
>> Well, how about this then:
>> [snip]
>
>
>Here's my shot at what would've helped me a lot when I initially faced
>problems.  Of course providing as much info as below will only leave
>you with more newbies crying 'cygwin_split_path() : 0x61073e06' or such.

I don't think the cygwin FAQ should tell people how to debug.

My intent for the FAQ was only to mention that normal cygwin DLLs do not
contain enough information for a backtrace to be useful.

I do not want to imply that we will help people debug either the cygwin DLL
or their applications in gdb.  I was just hoping to provide some clarification
to people who already know about gdb but do not know that the cygwin DLL
is stripped.

Joshua, do you think you could rejigger the entry to just say something like
the above?  It doesn't have to be a long entry and it doesn't have to
try to help people run the debugger.

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/