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

Mocking the VS side (in python or C++) sounds like the way to go. I don't know much smartness is in this code (as in, something other than "take this json, translate it to an appropriate SB call and serialize the results back"), but if there is some non-trivial logic in there (perhaps the code for

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

+ eugene as the "most recent person who worked on the DYLD plugin" :D Hi Dmitry, I've tried your sample, and I was indeed able to reproduce the problem. What makes your case special is that "sin" and "cos" are indirect functions (STT_GNU_IFUNC), so we have to do some extra work (call the resolver

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

On 02/15/2018 02:21 PM, Pavel Labath wrote: I've tried your sample, and I was indeed able to reproduce the problem. What makes your case special is that "sin" and "cos" are indirect functions (STT_GNU_IFUNC), so we have to do some extra work (call the resolver function) to resolve them. I've

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

Yes, it looks that way, but I cannot reproduce this on my side (which is not surprising as it involves parsing debug info from your dynamic linker). I'd need the relevant portions of that file (or just the whole file) to see what's going on there. That said, this shouldn't impact you unless you pl

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

I've created a patch implementing this in . Let me know what you think of it (particularly of the parts that will become the "stable API"). On 14 February 2018 at 18:43, Greg Clayton wrote: > I second Jim's idea for a static function on SBDebugger that returns a

[lldb-dev] [Bug 36394] New: Unable to resolve pending breakpoint to an indirect (STT_GNU_IFUNC) function

https://bugs.llvm.org/show_bug.cgi?id=36394 Bug ID: 36394 Summary: Unable to resolve pending breakpoint to an indirect (STT_GNU_IFUNC) function Product: lldb Version: 6.0 Hardware: PC OS: Linux S

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

> On Feb 15, 2018, at 3:56 AM, Dmitry Antipov via lldb-dev > wrote: > > On 02/15/2018 02:21 PM, Pavel Labath wrote: > >> I've tried your sample, and I was indeed able to reproduce the >> problem. What makes your case special is that "sin" and "cos" are >> indirect functions (STT_GNU_IFUNC), s

[lldb-dev] LLVM & GSoC 2018

Dear All, On behalf of LLVM Foundation it's my pleasure to announce to LLVM has been accepted to participate in Google Summer of Code program this year. The list of open projects could be found at http://llvm.org/OpenProjects.html#gsoc18 Please let me know, if: - You're LLVM contributor and wou

[lldb-dev] GSoC 2018

Hi, I'm student at NTUU KPI, Ukraine, and I would like to participate this summer in GSoC with LLVM, I'm interested in Reimplement LLDB's command-line commands using the public SB API project. I think I have skills to complete this project. On this weekend I plan to build the project and deep into

[lldb-dev] [Bug 36403] New: LLDB Data Formatter for References

https://bugs.llvm.org/show_bug.cgi?id=36403 Bug ID: 36403 Summary: LLDB Data Formatter for References Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement P