Re: [lldb-dev] Remote debug arm bare metal target with lldb - load executable to target

Sounds like you got close. What does your target look like when you type: (lldb) target list I forgot to mention one thing that we do for ELF files: We make sections named PT_LOAD[N] where in N starts at zero. We do this because this is essentially how dynamic loaders actually load the binar

Re: [lldb-dev] RFC: -flimit-debug-info + frame variable

> On Jul 23, 2020, at 5:15 AM, Pavel Labath wrote: > > On 22/07/2020 01:31, Jim Ingham wrote: >> >> >>> On Jul 21, 2020, at 9:27 AM, Pavel Labath >> > wrote: >>> I do see the attractiveness of constructing of a full compiler type. The >>> reason I am hesitant to go tha

Re: [lldb-dev] Break setting aliases...

> On Jul 23, 2020, at 1:51 AM, Pavel Labath wrote: > > On 22/07/2020 19:50, Jim Ingham wrote: >>> On Jul 22, 2020, at 12:34 AM, Pavel Labath wrote: >>> >>> The "--" is slightly unfortunate, but it's at least consistent with our >>> other commands taking raw input. We could avoid that by makin

Re: [lldb-dev] RFC: -flimit-debug-info + frame variable

On 22/07/2020 01:31, Jim Ingham wrote: > > >> On Jul 21, 2020, at 9:27 AM, Pavel Labath > > wrote: >> I do see the attractiveness of constructing of a full compiler type. The >> reason I am hesitant to go that way, because it seems to me that this >> would negate the two m

Re: [lldb-dev] Break setting aliases...

On 22/07/2020 19:50, Jim Ingham wrote: >> On Jul 22, 2020, at 12:34 AM, Pavel Labath wrote: >> >> The "--" is slightly unfortunate, but it's at least consistent with our >> other commands taking raw input. We could avoid that by making the >> command not take raw input. I think most of the "modes"