Bug#163622: xfree86-common: Error starting X, using Matrox G200

[Michel Dänzer <daenzer@debian.org>]

On Die, 2002-10-08 at 18:52, Branden Robinson wrote: 
> On Mon, Oct 07, 2002 at 08:55:26PM -0400, Ian Bicking wrote:
> > Here's the backtrace, tell me if there's anything more you need:
> [...]
> > #7  0x0807f3c8 in xf86SigHandler (signo=11) at xf86Events.c:1085
> >         signo = 11
> > #8  0x4007e518 in sigaction () from /lib/libc.so.6
> > No symbol table info available.
> > #9  0x40197cdc in ?? ()
> > No symbol table info available.
> > #10 0x0852b478 in ?? ()
> > No symbol table info available.
> > #11 0x0806cabb in InitOutput (pScreenInfo=0x81cbc00, argc=5,
> > argv=0xbffffdf4)
> >     at xf86Init.c:528
> >         i = 1075228112
> >         j = 0
> >         k = 1074540038
> >         scr_index = 1074540038
> > No symbol table info available.
> 
> Figures.  Died in one of the modules, which are invisible to gdb.
> 
> The only way to nail this down is to use the specially-hacked version of
> gdb that understand XFree86 server modules.

Well, you can call LoaderPrintSymbol for each address with a ??, e.g.

call LoaderPrintSymbol(0x40197cdc)

Beware that the output goes to the server log only.


> Unfortunately, Debian's gdb does not contain this hack.

Hopefully, the patch will be cleaned up and applied soon; it would
certainly make debugging X much easier.


PS: I hope the submitter doesn't get this twice?

PPS: Quite some additional traffic on the list...

-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast