<div class="gmail_quote">Hi Dbus members,<div><br></div><div>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.</div>
<div>---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------</div>
<div><div>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</div>
<div><br></div><div>01-02 19:46:10.363 404 453 F libc : Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)</div><div><br></div><div>01-02 19:46:10.873 181 181 I DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***</div>
<div><br></div><div>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'</div><div><br></div><div>01-02 19:46:10.873 181 181 I DEBUG : pid: 404, tid: 453 >>> system_server <<<</div>
<div><br></div><div>01-02 19:46:10.873 181 181 I DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad</div></div><div>---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
</div><div><br></div><div>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 <b>fault addr deadbaad</b> which means heap got corrupted which could be elsewhere in the code. </div>
<div><br></div><div>Is this a known issue. Has this already been fixed. If yes, can I get the patch which fixes this issue.</div><div><br></div><div>"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."</div><div>OR</div><div>"Someone freed the memory which it doesn't own causing heap corruption"</div><div><br></div><div>I appreciate if someone can help me on this.</div>
<div><br></div><div>Thanks much in advance.</div><span class="HOEnZb"><font color="#888888"><div>Ankit</div>
</font></span></div><br>