Hi Greg,
I've been assuming that we can't force a change to openocd's behavior,
or at least that the easier path is to handle its current behavior. I
don't know why openocd sends O packets in response to an rCmd, but it
does and gdb is okay with it.
I'm still learning my way around the lldb code
> On Jan 1, 2018, at 6:30 PM, Owen Shaw via lldb-dev
> wrote:
>
> 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 are
Hello everyone,
The release branch for 6.0.0 was created from trunk at r321711 around
3pm GMT today, and the trunk version was subsequently incremented to
7.0.0. (Hopefully the git mirror will have the branch soon too.)
Note that this time we're doing an early "slow start" of the release
process.
I've prepared a report of the past month on MSan:
https://blog.netbsd.org/tnf/entry/the_llvm_memory_sanitizer_support
This is work in progress and I will keep working on MSan. I can already
sanitize trivial programs, but not the larger ones. Sanitizing
LLDB/NetBSD with MSan is still distant.
s
