Re: [lldb-dev] LLDB tests getting stuck on GDBRemoteCommunicationClientTest.GetMemoryRegionInfo ?

2018-05-02 Thread Pavel Labath via lldb-dev
Right, I see what's going on now. Yes, you're right, the commit you mention has added extra packets which are not handled in the mock. The reason this is hanging for you is because you are using a debug build, which has a much larger packet timeout (1000s i think). In the release build this passes,

Re: [lldb-dev] LLDB tests getting stuck on GDBRemoteCommunicationClientTest.GetMemoryRegionInfo ?

2018-05-02 Thread Pavel Labath via lldb-dev
Ok, r331374 ought to fix that. The situation was a bit more complicated then I thought, because the function was behaving differently if one builds lldb with xml support, so i've had to update the test to work correctly in both situations. On Wed, 2 May 2018 at 16:34, Pavel Labath wrote: > Right,

Re: [lldb-dev] LLDB tests getting stuck on GDBRemoteCommunicationClientTest.GetMemoryRegionInfo ?

2018-05-02 Thread Leonard Mosescu via lldb-dev
Great, thanks Pavel! On Wed, May 2, 2018 at 10:06 AM, Pavel Labath wrote: > Ok, r331374 ought to fix that. The situation was a bit more complicated > then I thought, because the function was behaving differently if one builds > lldb with xml support, so i've had to update the test to work correc

[lldb-dev] [Bug 37317] New: ModuleList::FindGlobalVariables fails with append=false

2018-05-02 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=37317 Bug ID: 37317 Summary: ModuleList::FindGlobalVariables fails with append=false Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW