Bug#804694: libqt5xcbqpa5 SIGSEGV crashes sporadically at QXcbWindow::handleClientMessageEvent
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 11.11.2015 16:05, Dmitry Shachnev wrote:
> It would be nice if you could provide a more useful stacktrace (i.e. with qtbase5-dbg installed).
Hi Dmitry,
Oh sure, sorry for that. Here it is:
Program received signal SIGSEGV, Segmentation fault.
0x00007fffe1a6e94f in QXcbWindow::handleClientMessageEvent (this=0x555555da6f80, event=0x7fffd8003e00) at qxcbwindow.cpp:1942
1942 qxcbwindow.cpp: No such file or directory.
(gdb) bt
#0 0x00007fffe1a6e94f in QXcbWindow::handleClientMessageEvent (this=0x555555da6f80, event=0x7fffd8003e00) at qxcbwindow.cpp:1942
#1 0x00007fffe1a59b2b in QXcbConnection::handleXcbEvent (this=this@entry=0x555555b9bdd0, event=event@entry=0x7fffd8003e00)
at qxcbconnection.cpp:1066
#2 0x00007fffe1a5a053 in QXcbConnection::processXcbEvents (this=0x555555b9bdd0) at qxcbconnection.cpp:1502
#3 0x00007ffff2e777f1 in QObject::event (this=0x555555b9bdd0, e=<optimized out>) at kernel/qobject.cpp:1239
#4 0x00007ffff373c9dc in QApplicationPrivate::notify_helper (this=this@entry=0x555555b91110, receiver=receiver@entry=0x555555b9bdd0,
e=e@entry=0x7fffd80035b0) at kernel/qapplication.cpp:3716
#5 0x00007ffff3741ea6 in QApplication::notify (this=0x7fffffffdc00, receiver=0x555555b9bdd0, e=0x7fffd80035b0)
at kernel/qapplication.cpp:3499
#6 0x00007ffff2e47dbb in QCoreApplication::notifyInternal (this=0x7fffffffdc00, receiver=0x555555b9bdd0,
event=event@entry=0x7fffd80035b0) at kernel/qcoreapplication.cpp:965
#7 0x00007ffff2e4a1b6 in QCoreApplication::sendEvent (event=0x7fffd80035b0, receiver=<optimized out>)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#8 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x555555b8dbf0)
at kernel/qcoreapplication.cpp:1593
#9 0x00007ffff2e4a698 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0)
at kernel/qcoreapplication.cpp:1451
#10 0x00007ffff2e9e163 in postEventSourceDispatch (s=0x555555bc2d50) at kernel/qeventdispatcher_glib.cpp:271
#11 0x00007ffff08bdfe7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff08be240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff08be2ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff2e9e56f in QEventDispatcherGlib::processEvents (this=0x555555bc2aa0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#15 0x00007ffff2e4554a in QEventLoop::exec (this=this@entry=0x7fffffffdb60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#16 0x00007ffff2e4d62c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229
#17 0x0000555555671736 in main ()
> Also, do you know if it is a new bug in Qt 5.5, or did it exist with Qt 5.4 too?
I think yes, this started with 5.5.
I'm running Debian testing for more than 3 years, reinstalled stretch on a new notebook months ago (April).
It never crashed like this.
Cheers
Markus Frosch
- --
markus@lazyfrosch.de / lazyfrosch@debian.org
http://www.lazyfrosch.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWRJGuAAoJEPJhXZqrmHtugfcIAMUG7/OQx+R8eGoxf0DBrjBH
DbOE1I339ni0VBjEkrScdACrRsHbQBtGamkok9Twp2o1N3hIWORIIXXx0iL4bghZ
0O67ejCgSguibYHbvie8Lwm4caodNPaiuugLs32SK7G3Fr4G8/1JYLPGw02S8WAn
VdHmS6bBxOW2oGUNl3I43BhEtkZuj/SacWzkX4H4CADLD1IIK76oJxLdqMUItHDI
Eg2vs+hBLZ0gCYUJCCvXmNIWdga3zAm0xyhGx7nKju7//UxqZ2EhiW9zOAgsuTlS
LsHCN/EW9cdzzdpVyNYsMXjvKjzdsfl+1v/O1F3oYkKulNDk5RzKFTQ9JaJIpeg=
=bODu
-----END PGP SIGNATURE-----
Reply to: