libdbus : 404: assertion failed "(connection)->have_connection_lock" file "external/dbus/dbus/dbus-connection.c"

Ankit Verma shiningankit at gmail.com
Fri Jan 20 13:26:15 PST 2012


Hi Dbus members,

I am sorry if this is a wrong forum to ask any queries. But, I am seeing
the following error message in the android logcat after which system_server
crashes.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
01-02 19:46:10.222   404   453 W libdbus : 404: assertion failed
"(connection)->have_connection_lock" file
"external/dbus/dbus/dbus-connection.c" line 793 function
protected_change_timeout

01-02 19:46:10.363   404   453 F libc    : Fatal signal 11 (SIGSEGV) at
0xdeadbaad (code=1)

01-02 19:46:10.873   181   181 I DEBUG   : *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***

01-02 19:46:10.873   181   181 I DEBUG   : Build fingerprint:
'qcom/msm8960/msm8960:4.0.3/IML74K/eng.parkj.20120118.145253:eng/test-keys'

01-02 19:46:10.873   181   181 I DEBUG   : pid: 404, tid: 453  >>>
system_server <<<

01-02 19:46:10.873   181   181 I DEBUG   : signal 11 (SIGSEGV), code 1
(SEGV_MAPERR), fault addr deadbaad
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


I have seen people posting about this over the internet. But, I didn't get
any idea about whats going wrong. There was also a discussion about the *fault
addr deadbaad* which means heap got corrupted which could be elsewhere in
the code.

Is this a known issue. Has this already been fixed. If yes, can I get the
patch which fixes this issue.

"Looks like Dbus acquired a lock in a connection and then got interrupted,
reentered, locked again and unlocked, then resumed. At that point, the lock
was cleared, hence the assertion."
OR
"Someone freed the memory which it doesn't own causing heap corruption"

I appreciate if someone can help me on this.

Thanks much in advance.
Ankit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dbus/attachments/20120120/fe93e195/attachment.html>


More information about the dbus mailing list