Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

Thanks! I've added the binaries to http://prereleases.llvm.org/6.0.0/ On Tue, Feb 13, 2018 at 10:57 PM, Simon Dardis wrote: > Hi Hans, > > I'm seeing one unexpected failure: > > libc++ :: > std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp >

Re: [lldb-dev] Querying build configuration of (lib)lldb from tests.

The idea of having a static function in SBDebugger that returns lldb configuration information seems good to me. Having the API return an SBStructuredData with the full configuration information seems like a pretty future-proof way to do this. I can't see that this data will get sufficiently l

Re: [lldb-dev] Querying build configuration of (lib)lldb from tests.

I second Jim's idea for a static function on SBDebugger that returns a SBStructuredData > On Feb 14, 2018, at 10:31 AM, Jim Ingham via lldb-dev > wrote: > > The idea of having a static function in SBDebugger that returns lldb > configuration information seems good to me. > > Having the API r

[lldb-dev] How to test lldb-vscode?

I have a patch I will be submitting soon that adds a tool called "lldb-vscode" that is much like "lldb-mi" where it sits on top of LLDB.framework on Darwin and liblldb.so on all other platforms, and it speaks the Visual Studio Code Debug adaptor language and can be used to create a VSCode extens

Re: [lldb-dev] How to test lldb-vscode?

FYI - I've been maintaining a similar VSCode extension , which does it all through LLDB's Python interface. As for testing, the protocol is JSON with HTTP-like headers for framing, so you could have a Python script emulating

Re: [lldb-dev] How to test lldb-vscode?

> On Feb 14, 2018, at 3:45 PM, Vadim Chugunov wrote: > > FYI - I've been maintaining a similar VSCode extension > , > which does it all through LLDB's Python interface. Indeed, I saw you plug-in and since it worked so

Re: [lldb-dev] How to test lldb-vscode?

My tests are here . I probably wouldn't move all that to Python for my extension, but feel free to draw ideas on things to test from it. What's going to be your deployment story? The nice thing about Python-based

Re: [lldb-dev] How to test lldb-vscode?

The SB API's were designed to be binary stable API's when used either from C++ or Python (the latter are just a SWIG-ified version of the former.) So just like the Python wrapper, with the exception that you might call an API that some older version of liblldb doesn't provide, Greg's adaptor wo

[lldb-dev] Pending breakpoints to dlsym()ed functions

I'm trying to setup a pending breakpoint for sin() and cos() which are dlsym()ed from libm.so (sample attached), and an attempt to continue execution seems just hangs the debugger. For example: (lldb) attach 17043 Process 17043 stopped * thread #1, name = 't-dlopen', stop reason = signal SIGSTO