[lldb-dev] Forking fixes in the context of debuggers

For the past month I've been mostly working on improving the kernel code in the ptrace(2) API. Additionally, I've prepared support for reading NetBSD/aarch64 core(5) files. A critical Problem Report kern/51630 regarding lack of PTRACE_VFORK implementation has been fixed. This means that there are

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

PS. just a wild guess, could it be related to : rL327970: Re-land: [lldb] Use vFlash commands when writing to target's flash memory… ? On Tue, May 1, 2018 at 1:24 PM, Leonard Mosescu wrote: > Thanks Pavel. It doesn't look like a timeout to me: > > 1. First, the other (main) thread is just waitin

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

Thanks Pavel. It doesn't look like a timeout to me: 1. First, the other (main) thread is just waiting on the std::future::get() on the final EXPECT_TRUE(result.get().Success()) *#0 0x7fe4bdfbb6cd in pthread_join (threadid=140620333614848, thread_return=0x0) at pthread_join.c:90* *...* *#14 0

Re: [lldb-dev] Proposal: Using LLD in tests

I have created a patch , which extends lldb-test to support more precise dumping of the symbol information in a module. It uses lld to make sure the tests can run on any system (which has lld checked out) and to avoid the tests being affected by the environment. Let

Re: [lldb-dev] Dlopen extremely slow while LLDB is attached

> This is a known issue, though I did not expect it to have that much of an > impact. In fact, I have trouble reconciling this fact with your earlier > statement that second and subsequent runs are much faster. The SO entry > loading is something that has to happen on every run, so I don't see why

Re: [lldb-dev] Dlopen extremely slow while LLDB is attached

On Mon, 30 Apr 2018 at 20:13, Scott Funkenhauser wrote: > I messed up my test setup and incorrectly attributed the additional time. Parsing the DWARF sections does add additional time, but only increases by a small percentage. > By pure chance I noticed that the latency between the client and se

[lldb-dev] [Bug 37301] New: Unable to display statically initialized pointers on arm64 (linux?) without a running process

https://bugs.llvm.org/show_bug.cgi?id=37301 Bug ID: 37301 Summary: Unable to display statically initialized pointers on arm64 (linux?) without a running process Product: lldb Version: unspecified Hardware: PC