assertion failed "!(connection)->have_connection_lock"
Thiago Macieira
thiago at kde.org
Sun Aug 9 07:07:54 PDT 2009
Jean-Christian de Rivaz wrote:
>Hi all,
>
>While working on a ARM I have an application that sometime locked into a
>infinite loop into the libdbus. I added the --enable-asserts to debug
>this and since I get this message:
>389: assertion failed "!(connection)->have_connection_lock" file
>"dbus-connection.c" line 2519 function dbus_connection_ref
>
>This was with the dbus version 1.2.12. I have found a threads into the
>mailing list about this error:
>http://lists.freedesktop.org/archives/dbus/2007-July/008102.html
>A some point someone proposed a patch:
>http://lists.freedesktop.org/archives/dbus/2007-July/008126.html
>I tryed the modifications of this patch but this do not solved to
>problem for me. I also noticed that the patch was not present in the new
>1.3.0 version, so I assumed that this was solved an other way.
>
>So I tryed the new 1.3.0 revision and I still get it, only the line
>number change:
>389: assertion failed "!(connection)->have_connection_lock" file
>"dbus-connection.c" line 2567 function dbus_connection_ref
>
>The application basically get a lot of UNIX signals (about 10 per
>seconds) and a few dbus signals per seconds. It run some magic and
>sometime produce a dbus signal. The problem occur rarely, but alway at
>the same dbus_connection_flush() call.
Just so we're clear: by "run some magic and sometime produce a dbus
signal", you don't mean inside the Unix signal handlers, right?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freedesktop.org/archives/dbus/attachments/20090809/23237acd/attachment.pgp
More information about the dbus
mailing list