[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#442395: xserver-xorg-core: hitting certain operation in digikam busy-locks xserver



David Schmitt wrote:
> title 442395 xserver-xorg-core: hitting certain operation in digikam 
> busy-locks xserver
> found 442395 2:1.4-2
> thanks
>
> Hi!
>
> Please find attached a full backtrace of the running XServer, when it is 
> spinning. I broke into gdb by sending the XServer a SIGINT.
>
> Regards, David
>   
> ------------------------------------------------------------------------
>
> zion:~# gdb /usr/bin/X
> GNU gdb 6.6.90.20070912-debian
> Copyright (C) 2007 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i486-linux-gnu"...
> (no debugging symbols found)
> Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
> (gdb) attach 32232
> Attaching to program: /usr/bin/X, process 32232
> Cannot access memory at address 0x665
> (gdb) cont
> Continuing.
> Program received signal SIGINT, Interrupt.
> 0x08106900 in ?? ()
> (gdb) set logging overwrite on
> (gdb) set logging on
> Copying output to gdb.txt.
> (gdb) bt full
> #0  0x08106900 in ?? ()
> No symbol table info available.
> #1  0xcf754637 in ?? ()
> No symbol table info available.
> #2  0x3e47d9f4 in ?? ()
> No symbol table info available.
> #3  0x00000000 in ?? ()
> No symbol table info available.
> (gdb) set logging off
>
>   

That's it? Nothing else? Make sure you have xserver-xorg-core-dbg
installed, it should help gdb.

Brice





Reply to: