[Lldb-commits] [PATCH] D13058: LLDB-MI: Bug when evaluating strings containing characters from non-ascii range

Eugene Leviant via lldb-commits lldb-commits at lists.llvm.org
Tue Sep 22 11:40:26 PDT 2015

evgeny777 added a comment.

Yes I know about GetValue() and stuff
Actually I implemented new method, because I needed TypeSummaryImpl::DoesPrintValue().
In lldb when you evaluate char*, you get both value and summary, for example:

0xdeadbeef "hello"

But when you evaluate char[] array, you get just "hello". Value is not printed, because DoesPrintValue() method returns false
The same is for UTF-16 characters (char16_t). This type has both value and summary, but only summary is printed by lldb

I wanted to replicate the same behavior in lldb-mi. But if adding methods to SBValue should be avoided, I'll think of some workaround inside lldb-mi.
Your opinions are welcome, of course


More information about the lldb-commits mailing list