[lldb-dev] SBThread::IsStopped() always returns false on Linux
Pavel Labath
labath at google.com
Fri Jun 5 15:04:13 PDT 2015
Hi,
thanks for the feedback. We are tracking this problem, and we
currently have some tests XFAILed because of this (I don't think the
issue is linux-specific). As a workaround for now, I think you can
assume all threads are stopped if process state is eStateStopped.
cheers,
pl
On 5 June 2015 at 14:43, Eugene Birukov <eugenebi at hotmail.com> wrote:
> OOPS, on server I tried wrong class, that's why the method is not here.
> Still, client inspects local m_state to make the call, and it is "unloaded"
> in cases I inspected.
>
> ________________________________
> From: eugenebi at hotmail.com
> To: lldb-dev at cs.uiuc.edu
> Date: Fri, 5 Jun 2015 14:28:22 -0700
> Subject: [lldb-dev] SBThread::IsStopped() always returns false on Linux
>
>
> Hi,
>
> I am running lldb-4.7 that I built from sources on Linux Ubuntu 14.04.
>
> I am using C++ API to debug my program. The program runs into different
> events: breakpoints I set, signals. But all threads always returnIsStopped()
> as false in any program state. I traced this call and it seems that the
> thread state is eStateUnloaded. The only place I found that changes thread
> state in Thread.cpp is this method:
>
> void
> Thread::SetState(StateType state)
> {
> Mutex::Locker locker(m_state_mutex);
> m_state = state;
> }
>
>
> So, I put breakpoint there and it is never hit. I tried to put similar
> breakpoint in lldb-server, but it seems that the method is not present here:
>
> (gdb) b lldb_private::Target::SetS
> SetSectionLoadAddress(std::shared_ptr<lldb_private::Section> const&,
> unsigned long, bool)
> SetSectionUnloaded(std::shared_ptr<lldb_private::Section> const&)
> SetSectionUnloaded(std::shared_ptr<lldb_private::Section> const&, unsigned
> long)
> SetStopHookActiveStateByID(unsigned long, bool)
> (gdb) b lldb_private::Target::SetState
> Function "lldb_private::Target::SetState" not defined.
> Make breakpoint pending on future shared library load? (y or [n])
>
>
> So far, this seems broken to me.
>
> Thanks,
> Eugene
>
> _______________________________________________ lldb-dev mailing list
> lldb-dev at cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
More information about the lldb-dev
mailing list