qt4 and xcb

S.Çağlar Onur caglar at pardus.org.tr
Fri Feb 23 05:04:15 PST 2007


22 Şub 2007 Per tarihinde, S.Çağlar Onur şunları yazmıştı: 
> > We are using vanilla qt4 yes.
>
> qt-copy patches seems not responsible at first sight, recompiling qt4 much
> more sense to me. Thanks for advice.

Still no luck, recompiling with debug symbols gaves following backtrace (all 
examples bundles with qt source also gaves same bt);

[caglar at zangetsu][~]> ldd /usr/bin/designer-qt4 | grep xcb
        libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0xb6ee6000)
        libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb6ecd000)

[caglar at zangetsu][~]> gdb designer-qt4
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run -dograb
Starting program: /usr/bin/designer-qt4 -dograb
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225111856 (LWP 11903)]
designer-qt4: xcb_xlib.c:41: xcb_xlib_lock: Sav `!c->xlib.lock' başarısızlığa 
uğradı.

Program received signal SIGABRT, Aborted.
[Switching to Thread -1225111856 (LWP 11903)]
0xb7fd57f2 in QWidget::inputMethodEvent () from /lib/ld-linux.so.2
(gdb) bt
#0  0xb7fd57f2 in QWidget::inputMethodEvent () from /lib/ld-linux.so.2
#1  0xb701cffe in raise () from /lib/libc.so.6
#2  0xb711eff4 in ?? () from /lib/libc.so.6
#3  0xb6fa46d0 in ?? ()
#4  0xb701e8ce in abort () from /lib/libc.so.6
#5  0x080fba90 in ?? ()
#6  0xb7120120 in __after_morecore_hook () from /lib/libc.so.6
#7  0x0000005e in ?? ()
#8  0xb705cd31 in realloc () from /lib/libc.so.6
#9  0xb7120120 in __after_morecore_hook () from /lib/libc.so.6
#10 0x080fba90 in ?? ()
#11 0x0000005e in ?? ()
#12 0x080fba88 in ?? ()
#13 0x00000068 in ?? ()
#14 0x080fba90 in ?? ()
#15 0xb711eff4 in ?? () from /lib/libc.so.6
#16 0x0000005e in ?? ()
#17 0x080fba90 in ?? ()
#18 0x0000005d in ?? ()
#19 0xb7051f31 in vasprintf () from /lib/libc.so.6
#20 0x080fba90 in ?? ()
#21 0x0000005e in ?? ()
#22 0xbfe26080 in ?? ()
#23 0x080fba90 in ?? ()
#24 0x00000000 in ?? ()
(gdb)  

Could you please check your qt4/qt4 apps linked against libxcb? Assuming qt4 
has no problem with libxcb, if anyone has another suggestion what may cause 
that problem i really want to hear?

Cheers
-- 
S.Çağlar Onur <caglar at pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20070223/006e9499/attachment.pgp>


More information about the xorg mailing list