[lldb-dev] target and host with different endianness

We have a big-endian target that we debug from LLDB running on Windows through a custom process plugin and communication protocol. The target's default byte order is set to eByteOrderBig in 'g_core_definitions' in ArchSpec.cpp. Most features work correctly (registers, variables, breakpoints, d

[lldb-dev] Prefered way to identify target device in tests?

I'm working on getting the tests running with Hexagon, and have a question about identifying the target architecture. Hexagon LLVM doesn't use a couple architectures like "x86_64" or "i386", instead we have many architectures, like "v4", "v5", "v55", "v56", v60", so using self.getArchitecture()

[lldb-dev] [Bug 26583] New: lldb lacks an equivalent to gdb's "directory" command

https://llvm.org/bugs/show_bug.cgi?id=26583 Bug ID: 26583 Summary: lldb lacks an equivalent to gdb's "directory" command Product: lldb Version: unspecified Hardware: PC OS: FreeBSD Status: NEW Severity: no

[lldb-dev] Making a new symbol provider

Hi, I want to make a new symbol provider to teach LLDB to understand microsoft PDB files. I've been looking over the various symbol APIs, and I have a few questions. 1. Under what circumstances do I need a custom SymbolVendor? The way pdb works is that generally there is 1 file that contains al

Re: [lldb-dev] Making a new symbol provider

> On Feb 11, 2016, at 3:41 PM, Zachary Turner via lldb-dev > wrote: > > Hi, > > I want to make a new symbol provider to teach LLDB to understand microsoft > PDB files. I've been looking over the various symbol APIs, and I have a few > questions. > > 1. Under what circumstances do I need

Re: [lldb-dev] target and host with different endianness

> On Feb 11, 2016, at 7:55 AM, Philippe Lavoie via lldb-dev > wrote: > > > We have a big-endian target that we debug from LLDB running on Windows > through a custom process plugin and communication protocol. > > The target's default byte order is set to eByteOrderBig in > 'g_core_definition

Re: [lldb-dev] Making a new symbol provider

On Thu, Feb 11, 2016 at 5:35 PM Greg Clayton wrote: > > > On Feb 11, 2016, at 3:41 PM, Zachary Turner via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > > > Hi, > > > > I want to make a new symbol provider to teach LLDB to understand > microsoft PDB files. I've been looking over the various sy

[lldb-dev] [Bug 26592] New: [LLDB][MIPS] TestInferiorAssert tests fail if section .gnu_debuglink is not available in libc.so.6

https://llvm.org/bugs/show_bug.cgi?id=26592 Bug ID: 26592 Summary: [LLDB][MIPS] TestInferiorAssert tests fail if section .gnu_debuglink is not available in libc.so.6 Product: lldb Version: unspecified Hardware: PC