This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.

Index Nav: Message Nav: [Date Index] [Subject Index] [Author Index] [Thread Index] [Date Prev] [Date Next] [Thread Prev] [Thread Next]

# Re: What's a good stable snapshot DLL?

On Mon, Apr 16, 2001 at 01:40:56PM -0400, DJ Delorie 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.

Yeah, I've been thinking about doing this.  Most of the debugging seems
like common sense, to me.  You set breakpoints and hope that they get
hit...

Or, you

set CYGWIN=error_start=x:\path\to\gdb.exe

and let cygwin pop up a copy of gdb when there is a SIGSEGV or something.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple



Index Nav: Message Nav: [Date Index] [Subject Index] [Author Index] [Thread Index] [Date Prev] [Date Next] [Thread Prev] [Thread Next]