[lldb-dev] segmentation fault occurs when pthread_mutex_lock tries to lock a mutex
triple.yang at gmail.com
Thu Jan 2 05:02:15 PST 2014
Thank you very much, *Granata.*
I did not construct frame unwinder for my target ISA in
lldb_private::Thread::GetUnwinder(), and thus it returned a null pointer.
2013/12/31 Enrico Granata <egranata at apple.com>
> Is it me or 0x10 is not a valid address?
> 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.
> You might want to check along the stack if you are accessing a NULL object
> without checking first.
> Sent from the iPhone of
> *Enrico Granata* <egranata@🍎.com>
> On Dec 31, 2013, at 3:44 AM, 杨勇勇 <triple.yang at gmail.com> wrote:
> Hi, all.
> I am porting lldb for a VLIW target with host env gcc-4.8.2/redhat
> enterprise linux 6.2.
> 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).
> I am not familiar with mutex errors, does anyone have clues?
> *Thanks in advance!*
> 杨勇勇 (Yang Yong-Yong)
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
杨勇勇 (Yang Yong-Yong)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev