Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<199902210642.AAA01410@modi.xraylith.wisc.edu>
X-Authentication-Warning:	modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To:	Murli Ganeshan <murli AT juno DOT com>
cc:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: gdb failure
In-reply-to:	Your message of "Sun, 21 Feb 1999 23:31:50 CST."
	<19990221 DOT 233151 DOT -251785 DOT 0 DOT murli AT juno DOT com>
Date:	Sun, 21 Feb 1999 00:42:45 -0600
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Murli Ganeshan <murli AT juno DOT com> writes:
> Here's a transcript of a gdb session while trying to debug an ACCESS
> VIOLATION bug.
> 
> (gdb) br test1
> Breakpoint 1 at 0x402654
> (gdb) r
> Starting program: /c/MSDEV/Projects/hmwk3/exam.exe 
> bff30000:/c/WINDOWS/SYSTEM/GDI32.DLL
> bff60000:/c/WINDOWS/SYSTEM/USER32.DLL
> bff70000:/c/WINDOWS/SYSTEM/KERNEL32.DLL
> bfed0000:/c/WINDOWS/SYSTEM/ADVAPI32.DLL
> 61000000:/c/CYGNUS/CYGWIN-B20/H-I586-CYGWIN32/BIN/CYGWIN1.DLL
> 
> Breakpoint 1, 0x402654 in test1 ()
> (gdb) s
> Single stepping until exit from function test1__Fv, 
> which has no line number information.

Try 1: compile with -g and see if you can debug it.
Try 2: There are bugs in the win32 version of gdb that disables stepping
into certain template instantiations. In this case, you may want to try
compiling with -ggdb (and perhaps -gstabs) and see if it helps.
Try 3: Mail me the code (the shortest possible piece that causes the 
problem), and perhaps I'll get a chance to look at it.

Let me apologize on behalf of all who support win32 for the lack of
support in gdb for debugging template instantiations. We need to get
this fixed, but nobody has volunteered yet.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -