On Thu, 2002-06-27 at 10:30, Sergey V. Udaltsov wrote: > I've tried to use remote debugging and got the backtrace of the SIGSEVG: > > Program received signal SIGSEGV, Segmentation fault. > 0x0841e74e in ?? () > (gdb) bt > #0 0x0841e74e in ?? () > #1 0x083fbca7 in ?? () > #2 0x083198bb in ?? () > #3 0x080b7e05 in ProcCopyArea () > #4 0x080b58d7 in Dispatch () > #5 0x080c808d in main () > #6 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 > > Is it useful in any way? I'm afraid binary snapshots are stripped so I > did not expect too much info:(
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) and so on. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
