On Thu, 2001-11-29 at 13:14, Jacques GANGLOFF wrote: > Michel D�nzer wrote: > > > > I tried also to run X in a gdb console but the server hangs. > > > > You can only run the server inside gdb in a remote session as you can't > > interact with gdb otherwise. > > > > Beware that gdb normally doesn't grok XFree86 modules. A patched version > > 4.x is available from XFree86, patches for 5.x have been posted here. > > Alternatively, you can build a static server for debugging. > > I have backtraced the problem with the patched gdb and I got : > > (gdb) bt > #0 0x80a2e7c in AllocateArea () > #1 0x80a304d in localAllocateOffscreenArea () > #2 0x80a3969 in localAllocateOffscreenLinear () > #3 0x80a2b24 in xf86AllocateOffscreenLinear () > #4 0x84160f1 in ?? () > #5 0x8417139 in ?? () > #6 0x80a674f in xf86XVPutImage () > #7 0x82adf72 in ?? () > #8 0x82b43cf in ?? () > #9 0x82b2709 in ?? () > #10 0x80b0176 in Dispatch () > #11 0x80c02db in main () > #12 0x4006a2eb in __libc_start_main (main=0x80bfd78 <main>, argc=2, > ubp_av=0xbffff9f4, init=0x806cb54 <_init>, fini=0x817690c <_fini>, > rtld_fini=0x4000c130 <_dl_fini>, stack_end=0xbffff9ec) > at ../sysdeps/generic/libc-start.c:129
The '??'s are the interesting parts. IIRC you have to load the symbols for an XFree86 module with a special command. #4 and #5 are probably in the driver. To get more debug information, rebuild the code in question with makeg. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
