Bug#390172: Bug still exists in 1.1.1-17
Matthew Wakeling wrote:
> On Tue, 20 Feb 2007, Brice Goglin wrote:
>> Once the X server is stuck using 99% of CPU, could you try attaching a
>> GDB with something like:
>> *gdb* -p $(*pidof* *X*)
>> (as root). I should help us have an idea what's going on.
>
> I have gdb connected now. I'm afraid my experience with gdb is rather
> limited. In any case, I have a backtrace, unfortunately without any
> line numbers:
You will have to use a server recompiled with debugging symbols to get
line numbers. You can do that by looking at
http://wiki.debian.org/HowToGetABacktrace. Replace 'hello' with
'xserver-xorg-core'. Once it is built and installed, restart X, and
reattach gdb as previously. You should get more details in the backtrace.
> (gdb) backtrace
> #0 0x00002b9f1ab62fcd in X86EMU_exec () from
> /usr/lib/xorg/modules/libint10.so
> #1 0x00002b9f1ab527f5 in xf86ExecX86int10 () from
> /usr/lib/xorg/modules/libint10.so
> #2 0x00002b9f1ab5355c in xf86ExtendedInitInt10 () from
> /usr/lib/xorg/modules/libint10.so
> #3 0x00002b9f1aa2e213 in ATIPreInit () from
> /usr/lib/xorg/modules/drivers/atimisc_drv.so
> #4 0x000000000045f72c in InitOutput ()
> #5 0x0000000000430d8f in main ()
If you do 'c' for continue, wait a little bit, hit ctrl-c and look at
the backtrace again, do you get the same backtrace?
Try this a couple times. It might help us know which function is looping
endlessly.
This is already interesting anyway. There have been some problems with
x86emu recently. We'll see what you get with debugging enabled.
Thanks,
Brice
Reply to: