Re: [Dri-devel] SIGSEGV on VT switch

[Andy I. <ad...@he...>]

On Thu, Jun 27, 2002 at 11:48:40AM +0100, Sergey V. Udaltsov wrote:
> > The problem is that stock gdb doesn't know about XFree86 modules. There
> > are patched versions of gdb for that, but even so you can get more
> > information by calling the LoaderPrintSymbol function for each of the
> > addresses before a '??', i.e. at the gdb prompt:
> > 
> > call LoaderPrintSymbol(0x0841e74e)
> Really? I tried one more time. First of all, the stack trace is
> different this time (which is funny itself) and this LoaderPrintSymbol
> does not help much:
> **********************************************************
> (gdb) continue
> Continuing.
> 
> Program received signal SIGUSR1, User defined signal 1.
> 0x420e198e in select () from /lib/i686/libc.so.6
> (gdb) bt
> #0  0x420e198e in select () from /lib/i686/libc.so.6
> #1  0xffffffff in ?? ()
> #2  0x080b574a in Dispatch ()
> #3  0x080c808d in main ()
> #4  0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
> (gdb) cont
> Continuing.
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x0841efee in ?? ()
> (gdb) bt
> #0  0x0841efee in ?? ()
> #1  0x083fc3ef in ?? ()
> #2  0x08593603 in ?? ()
> #3  0x080fddd3 in ShmRegisterFbFuncs ()
> #4  0x080fedab in ShmRegisterFbFuncs ()
> #5  0x080b58d7 in Dispatch ()
> #6  0x080c808d in main ()
> #7  0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
> 
> (gdb) call LoaderPrintSymbol(0x08593603)
> $1 = 1
> (gdb) call LoaderPrintSymbol(0x083fc3ef)
> $2 = 1
> (gdb) call LoaderPrintSymbol(0x083fc3ef)
> $3 = 1
> (gdb) call LoaderPrintSymbol(0x0841efee)
> $4 = 1
> (gdb) cont
> Continuing.
> ****************************************************
> I dont't think this is more informative.

The output went into the /var/log/XFree86.0.log (or to the console where
you started the X server), not to the GDB screen.

This caught me the first time I tried to use it, too. :)

-andy