libdbus : 495: assertion failed "!(connection)->have_connection_lock" file "external/dbus/dbus/dbus-connection.c
Ankit Verma
shiningankit at gmail.com
Thu Mar 29 14:04:52 PDT 2012
Hi,
I am getting this assertion failure causing a crash on a android mobile
phone using DBUS 1.4.0.
W libdbus : 495: assertion failed "!(connection)->have_connection_lock"
file "external/dbus/dbus/dbus-connection.c" line 369 function
_dbus_connection_lock
01-02 09:44:10.580 495 1620 F libc : Fatal signal 11 (SIGSEGV) at
0xdeadbaad (code=1)
I have picked up below few patches from the community which could have
fixed this issue, but i am still seeing the issue.
1. dbus_bus_register: don't unref the messages with the lock held
2. _dbus_connection_message_sent: rename to _unlocked
3. Add _dbus_counter_notify and call it after every adjustment
4. Comment some places where it's OK to unref a message despite holding
locks
5. When attaching counters to messages, don't automatically notify
callbacks
6. Don't inline the contents of _dbus_connection_unlock
7. Don't finalize sent or dispatched messages while under the connection
lock
Can anyone suggest if this issue is already fixed on latest dbus and point
me to the patches which fixed it.
Thanks a lot,
Ankit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dbus/attachments/20120329/c80d70af/attachment.htm>
More information about the dbus
mailing list