From kde-commits Thu Jun 01 23:48:42 2006 From: Thiago Macieira Date: Thu, 01 Jun 2006 23:48:42 +0000 To: kde-commits Subject: Re: kdesupport/qt-dbus Message-Id: <200606020148.42602.thiago () kde ! org> X-MARC-Message: https://marc.info/?l=kde-commits&m=114920575700234 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1848655.1mOMk08F4e" --nextPart1848655.1mOMk08F4e Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Ralf Habacker wrote: >The problem i believe is, that QMutex:unlock() is called with a mutex >already unlocked and that QMutex:unlock() does not detect this case. Yes, it does. That's why it prints the warning in the first place. But it freezes the application because you were not supposed to unlock=20 anything at that point. So I ask again: which mutex is being unlocked and at which point in the=20 code? =2D-=20 Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org thiago.macieira (AT) trolltech.com Trolltech AS GPG: 0x6EF45358 | Sandakerveien 116, E067 918B B660 DBD1 105C | NO-0402 966C 33F5 F005 6EF4 5358 | Oslo, Norway --nextPart1848655.1mOMk08F4e Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQBEf3zaM/XwBW70U1gRAjljAJwJNQfKSikY4UA9jXv1gvXe7gGPhgCeJgrQ 2xFyvVlArUuHf2o+Gz1t1gc= =YEDx -----END PGP SIGNATURE----- --nextPart1848655.1mOMk08F4e--