[lldb-dev] GDB Remote target descriptions

Hi all, I've been adding support for the qXfer:features:read:target.xml message for our tools at $WORK and have run into a couple hiccups to puzzle over. First off, the request message as defined at

Re: [lldb-dev] Conditionally adding sources to the build

I am glad to see freebsd is making progress on this front. If you need any help with understanding how lldb-server works, feel free to shoot me a question. pl On 1 December 2016 at 23:00, Dmitry Mikulin wrote: > Thanks for the suggestions. > I’m working on native support

[lldb-dev] [Bug 31245] New: Assertion failed: (m_base_dwarf_cu->GetOffset() == die_ref.cu_offset), function GetDIE, file src/tools/lldb/source/Plugins/SymbolFile/DWARF/SymbolFileDWARFDwo.cpp, line 120

https://llvm.org/bugs/show_bug.cgi?id=31245 Bug ID: 31245 Summary: Assertion failed: (m_base_dwarf_cu->GetOffset() == die_ref.cu_offset), function GetDIE, file src/tools/lldb/source/Plugins/SymbolFile/DWARF/SymbolF

Re: [lldb-dev] Conditionally adding sources to the build

I have a slightly unrelated question: is there an easy way to cross-build, say, an ARM lldb, and run native tests on an ARM board same as what check-lldb does? The lldb test page only talks about running remote tests. No info on cross testing. Thanks! On Dec 2, 2016, at 2:29 AM, Pavel Labath

Re: [lldb-dev] Refactoring in LLDB Windows Plugin

Yeah, we have to fake the numbers, we have some sort of dummy mapping that converts Windows events to the UNIX equivalent that makes the most sense. It's kind of dumb, but that's the only thing that LLDB or gdb support. First half of the conversion is here: