assertion failed "!(connection)->have_connection_lock"
Jean-Christian de Rivaz
jc at eclis.ch
Fri Aug 7 15:52:15 PDT 2009
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.
How can I trace the cause of this problem ?
Best Regards,
Jean-Christian de Rivaz
More information about the dbus
mailing list