Hi Everyone,
I'm writing a gdb-server for a new architecture and need to be able to debug
lldb to track down issues. Unfortunately disk space is tight here and the llvm
debug build consumes north of 40Gb with debug symbols. Is there any way to
build *only* lldb with debug symbols (and no optimi
Hi Everyone,
I'm unable to resolve *symbolic* breakpoints on a gdb-remote target. Address
breakpoints work fine. I suspect this is probably some form of user-error, but
I've had no luck figuring it out on my own.
My target has llvm support and lldb has been patched to add a new target as
well.
b) gdb-remote
>
> ?
>
> --
> Ted Woodward
> Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
> Foundation Collaborative Project
>
> -Original Message-
> From: lldb-dev On Behalf Of Adrian Harri
rget. It sounds like the Dynamic Loader
> step is missing.
>
> Jim
>
>
>> On Nov 8, 2018, at 10:20 AM, Adrian Harris via lldb-dev
>> wrote:
>>
>> (lldb) file tile.elf
>> Current executable set to 'tile.elf' (cs).
>> (lldb) b main
n
> it runs. It is the job of the DynamicLoader plugin for whatever platform
> you are debugging to observe a process as it is getting launched and
> register where all the sections land memory. The section load map is the
> storage for this information. If that isn't ge
Hi Everyone,
I’ve added basic support for a new target (via gdb-remote) and now it is time
to add ABI support to lldb to improve the debug experience. My understanding is
that I need to add an ABI plugin (we have a very basic stub now) and
thread-plan support. As a first step I’d like to be abl
