Re: GDB errors

[Alan Hourihane <alanh at fairlite dot demon dot co dot uk>]

On Tue, Nov 06, 2001 at 02:12:16PM -0500, Christopher Faylor wrote:
> On Tue, Nov 06, 2001 at 07:01:19PM +0000, Alan Hourihane wrote:
> >On Mon, Nov 05, 2001 at 10:04:49PM +0000, Alan Hourihane wrote:
> >> On Mon, Nov 05, 2001 at 03:50:21PM -0500, Christopher Faylor wrote:
> >> > On Mon, Nov 05, 2001 at 01:56:31PM +0000, Alan Hourihane wrote:
> >> > >Anyone tried to use GDB to debug XWin lately ?
> >> > >
> >> > >I'm constantly getting this....
> >> > >
> >> > >Starting program: /X11R6/4.x/win-loader/xc/programs/Xserver/XWin.exe
> >> > >"/cygdrive/c/WINNT/system32/KERNEL32.dll": error reading line numbers
> >> > >"/cygdrive/c/WINNT/system32/ADVAPI32.dll": error reading line numbers
> >> > >"/cygdrive/c/WINNT/system32/RPCRT4.dll": error reading line numbers
> >> > >"/cygdrive/c/WINNT/System32/WINMM.dll": error reading line numbers
> >> > >"/cygdrive/c/WINNT/system32/VERSION.dll": error reading line numbers
> >> > >"/cygdrive/c/WINNT/system32/SHELL32.dll": error reading line numbers
> >> > >"/cygdrive/c/WINNT/system32/LZ32.dll": error reading line numbers
> >> > >warning: Lowest section in /cygdrive/c/WINNT/System32/sbENG32.dll is .rsrc at 10001000
> >> > >/cygnus/netrel/src/gdb-20010428-3/gdb/coffread.c:472: gdb-internal-error: sect_index_text not initialized
> >> > >Quit
> >> > >Internal GDB error: recursive internal error.
> >> > >Internal GDB error: recursive internal error.
> >> > 
> >> > Do you get the same problems with an older version of gdb?  I'm
> >> > just wondering if my recent gdb release (which you appear to be running)
> >> > caused some problems.
> >> 
> >> I've tried the 0428-1 release too, with pretty much the same results.
> >> 
> >> Do I need to go furthur back ?
> >> 
> >I've just tried to go furthur back, but alas, the 0428-1 and -3 releases
> >are the only ones available. Chris - Is there anything I can test for
> >you to track these gdb problems down ?
> 
> If you are running the 0428-1 release you shouldn't be seeing the "error
> reading line numbers" messages, at least.
> 
Correct. I don't. But gdb in both cases seems to stop, and I have to hit
CTRL+C to terminate and this is where the internal errors pop up.

> Otherwise, building gdb from the CVS head is a possibility.  There have
> been problems with insight that have prevented me from releasing a new
> version based on CVS but maybe 'gdb -nw' might work better.
> 
I always use -nw. So I'll try and grab the CVS.

> I will eventually release a gdb from CVS when everything seems stable,
> of course...
> 
I need to debug now really, so CVS is my only hope....

Alan.