oading. So do the right thing for ELF and it should all work
> out. Good to hear you are actively working on what should be in vaddr vs
> paddr.
>
> Greg
>
>
> -Owen
>
> On Tue, Jan 9, 2018 at 4:15 PM, Greg Clayton wrote:
>
>
> On Jan 9, 2018, at 3:53 PM, Owen S
Looks like there was an addition about a year ago to load an object
file to bare metal target memory via "target modules load --load".
https://reviews.llvm.org/D28804
However, this isn't working in my case with openocd and a target that
uses flash memory. By comparison, gdb loads the object just
rking option coded up, and can easily throw a patch up in
Phabricator if it'd be helpful to discuss the details. Let me know
how you'd like to proceed.
Thanks,
Owen
On Wed, Jan 3, 2018 at 11:11 AM, Greg Clayton wrote:
>
>> On Jan 1, 2018, at 6:30 PM, Owen Shaw via lldb-dev
I dug into this a bit more, and these output reply packets seem to be
handled already, but only if the program is running.
Since the relevant openocd commands are often issued when the program
paused, the reply packets aren't processed as expected.
The spec does say that reply packets can happen
Looking for guidance. This seems like an lldb issue, but maybe I'm
missing something. And while I have a potential solution, I'm not
familiar enough with lldb code to know if its a "good" solution.
Background
--
openocd sends mutliple "O XX..." reply packets
(https://sourceware.org/gdb/
