--nextPart5368145.YRrKmTq4tE
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Saturday, 5 de February de 2011 17:39:35 Dawit Alemayehu wrote:
> was that in both cases the backtrace shows QtDBus attempting to invoke or
> access some method or slot in the object that was just destroyed. At this

That's supposed to be impossible. QtDBus connects to the object's 
destroyed(QObject*) signal, and removes the object from the object tree when 
it's destroyed.

It's also thread-safe, as all manipulations of the object tree are done under 
a write lock.

The only thing I can think of is that something caused the signal to 
disconnect.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

--nextPart5368145.YRrKmTq4tE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iD8DBQBNTY+UM/XwBW70U1gRAkC1AKCYlgrsU3LGaGR4MhM0wRLd8h2q4wCePWfD
jWQqMTnIYy6RZ0GukML7Oig=
=douY
-----END PGP SIGNATURE-----

--nextPart5368145.YRrKmTq4tE--