Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 16 Apr 2001 14:36:19 -0400 From: Christopher Faylor To: Christopher Faylor Subject: Re: What's a good stable snapshot DLL? Message-ID: <20010416143619.A18970@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: Christopher Faylor References: <8F23E55D511AD5119A6800D0B76FDDE11E0F0A@cpex3.channelpoint.com> <200104161740.NAA13650@envy.delorie.com> <20010416135126.C17910@redhat.com> <81181541863.20010416222044@logos-m.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <81181541863.20010416222044@logos-m.ru>; from deo@logos-m.ru on Mon, Apr 16, 2001 at 10:20:44PM +0400 On Mon, Apr 16, 2001 at 10:20:44PM +0400, egor duda wrote: >Hi! > >Monday, 16 April, 2001 Christopher Faylor cgf@redhat.com wrote: > >>>> This is probably a FAQ. Are the cygwin1.dll snapshots generated >>>> with debug symbols such that I'll get more information in my Dr Watson >>>> reports? If not, do I need to build my own with VC++ 6.0 such that I >>>> can pull up the debugger when (if) I get the access violations? >>> >>>Snapshots are built with gcc, not vc, so even if there's debug >>>information in it, DrWatson won't see it. >>> >>>If you're going to be debugging the dll, you should get the sources >>>from CVS and built it yourself, and use gdb to debug. That will give >>>you the best environment. However, you'll need to build a copy of gdb >>>that uses a "debug" version of cygwin, so as to avoid using the dll >>>you're debugging. Chris - perhaps you should create a web page on how >>>you debug the dll? You've had the most experience with this. > >CF> Yeah, I've been thinking about doing this. Most of the debugging seems >CF> like common sense, to me. You set breakpoints and hope that they get >CF> hit... > >i think almost everything starts to seem like common sense after you >spent several days debugging some non-trivial bug in cygwin1.dll :-) >At least, from my experience. I'm not saying that there aren't special tricks that you learn as you are debugging gdb. However, most people can't seem to make it to step one -- run gdb. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple