Thanks for details! So at first I'll try to propagate the "language"
setting of an expression there.
On Wed, Oct 31, 2018 at 9:04 PM Jim Ingham wrote:
> We need to do more work to make sure the "language" setting for
> expressions gets propagated everywhere and obeyed. We could also be
> smarte
I'm new in plugin ecosystem, so I have some misunderstanding. You wrote
that to comprehend mutexes we just need a data formatter, but how can we
get the raw data of all mutexes in our OS? I thought I was supposed to
write a generic code that will use a user-defined (specific for each OS)
way to col
I don’t think we are disagreeing, probably I was just being a little too terse.
What I’m saying is that to PRESENT a mutex in some detail, we need an OS
specific data formatter, so in that case, we just need some agent, either the
Platform or the SystemRuntime (but the Platform seems better to
https://bugs.llvm.org/show_bug.cgi?id=39529
Bug ID: 39529
Summary: Stride Step – stepping multiple lines at once without
missing anything
Product: lldb
Version: unspecified
Hardware: All
OS: All
