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

2020-07-30 Thread Tatyana Krasnukha via lldb-dev
Try this: `target modules load --load --set-pc-to-entry --slide 0`. From: lldb-dev On Behalf Of via lldb-dev Sent: Wednesday, July 22, 2020 7:10 PM To: lldb-dev@lists.llvm.org Subject: [lldb-dev] Remote debug arm bare metal target with lldb - load executable to target Hello, we are trying

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

2020-07-23 Thread Greg Clayton via lldb-dev
aders. > The entry point address and program header addresses are all set correctly. > > > Von: Greg Clayton > Gesendet: Donnerstag, 23. Juli 2020 01:05 > An: lulle2007...@gmail.com > Cc: lldb-dev@lists.llvm.org > Betreff: Re: [lldb-dev] Remote debug arm bare metal targe

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

2020-07-22 Thread Greg Clayton via lldb-dev
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

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

2020-07-22 Thread via lldb-dev
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