<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Is it me or 0x10 is not a valid address?</div><div>At a glance, you get that kind of address when you are dereferencing an iVar of a zeroed-out pointer, and 16 would be the offset of the mutex from the base of the class.</div><div>You might want to check along the stack if you are accessing a NULL object without checking first.<br><br>Sent from the iPhone of<div><i>Enrico Granata</i> <egranata@đ.com></div></div><div><br>On Dec 31, 2013, at 3:44 AM, æšćć <<a href="mailto:triple.yang@gmail.com">triple.yang@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div>Hi, all.<br><br></div><div>I am porting lldb for a VLIW target with host env gcc-4.8.2/redhat enterprise linux 6.2.<br></div>This problem happens in member function lldb_private::Unwind::GetFrameInfoAtIndex() when it tries to lock member "m_unwind_mutex" whose runtime address is 0x10 (checked via GDB).<br>
</div><div><div><br clear="all"><div>I am not familiar with mutex errors, does anyone have clues?<br></div><div><span class=""><em>Thanks in advance!</em></span></div><div><br>-- <br>æšćć (Yang Yong-Yong)
</div></div></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>lldb-dev mailing list</span><br><span><a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a></span><br><span><a href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev">http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev</a></span><br></div></blockquote></body></html>