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

The --load option should work if all of the program headers have the right addresses. LLDB should try to load all PT_LOAD program headers into memory at the address that they are loaded at. Is this a baseboard situation where you have an ELF file that has program headers with all of the

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

BTW: to see what things expand to after reach regex alias, just set this setting first: (lldb) settings set interpreter.expand-regex-aliases true Each time you type "b main" it will show you the expansion: (lldb) b main breakpoint set --name 'main' ... (lldb) b main.cpp:12 breakpoint set

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

> On Jul 22, 2020, at 12:34 AM, Pavel Labath wrote: > > I use "b" for file+line breakpoints and "br set -n" for function > breakpoints, mainly because I couldn't be bothered to figure out how > that works with the "b" command. Now that I have studied the command > once again, I may try using

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

> On Jul 22, 2020, at 9:57 AM, Dave Lee wrote: > > On Tuesday, July 21, 2020, Jim Ingham via lldb-dev > wrote: > I think adding: > > bs (break source) -> break set -y > ba (break address) -> break set -a > bn (break name) -> break set -n > > would provide a

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

On Tuesday, July 21, 2020, Jim Ingham via lldb-dev wrote: > I think adding: > > bs (break source) -> break set -y > ba (break address) -> break set -a > bn (break name) -> break set -n > > would provide a convenient way to set the most common classes of > breakpoints while not precluding access

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

Hello, we are trying to debug firmware running on a stm32 using OpenOCD and LLDB. GNU-GDB provides a 'load' command to load the sections from an ELF file to the target device. We have tried to use 'target modules load --load' command to load ELF sections to a specific address, but that didn't

Re: [lldb-dev] [Release-testers] LLVM 10.0.1-final has been tagged

Hi, I have finished testing llvm-10.0.1-final on Power PC 64bit Little Endian Red Hat 7.4 machine and have uploaded the binary from IBM. The sha1 file is attached. Thanks, Ahsan Saghir. On Tue, 21 Jul 2020 at 01:25, Tom Stellard via Release-testers < release-test...@lists.llvm.org> wrote: >

Re: [lldb-dev] [Release-testers] LLVM 10.0.1-final has been tagged

Windows is ready: $ sha256sum LLVM-10.0.1-win*.exe 5d92025d246615b92b3fcf5661ebd2866f5668c065456066f2622933ca741b64 LLVM-10.0.1-win32.exe 126885205403490754a2555659ae52d792eedc8bb2091c09a952eac8642feb80 LLVM-10.0.1-win64.exe It was built with the attached batch file. On Tue, Jul 21, 2020 at

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

I use "b" for file+line breakpoints and "br set -n" for function breakpoints, mainly because I couldn't be bothered to figure out how that works with the "b" command. Now that I have studied the command once again, I may try using it for function breakpoints as well... I don't have any hard