Re: [C++] developers -- how you watch Unicode strings in debugger?
Re: [C++] developers -- how you watch Unicode strings in debugger?
- Subject: Re: [C++] developers -- how you watch Unicode strings in debugger?
- From: Yingshen Yu <email@hidden>
- Date: Fri, 13 Apr 2012 08:44:52 +0800
I am also eager to see native unicode support in GDB. We have a code base which is cross-platform with Windows, so wchar_t is the foundation type in our ode.
Speaking of this proposal, we might need send it to LLVM mailing list, specially LLDB. Apple has stopped updating GDB for years, LLDB is the future in XCode.
-Jonny
On 2012-4-13, at 上午6:45, Ruslan Zasukhin <email@hidden> wrote:
> Hi Sebastien,
> Hi Dmitry,
>
> I am 10 years users of xcode, and frankly saying both your answers are not
> much helpful to me :-( May be I need re-read this at morning tomorrow :)
>
>
> I really do not understand, what technical troubles exists to show us UTF-16
> string right in the place where we see variables.
>
> z (int) 5
> p (char*) "abcd"
> p2 (whcar_t*) "abcd" 4-bytes chars, UTF-32
> p3 (ushort*) "abcd" 2 bytes chars, UTF-16
>
> ??
>
> Text files can be encoded UTF8, UTF16 and UTF32.
> XCODE perfectly is able show us this in editor.
>
> What problems show us these strings in debugger?
>
> Than more that LLVM has "View Variable as UTF16",
> But instead of string it show numbers:
> "05 06" "24 06"
>
> Why not just "CD"?
>
> MS Visual C++ do this perfectly. For years ...
> So there is no technical problems ...
> WE must get this just from box. Automatically.
>
> XCODE itself show us these chars in the MEMORY Browser.
> Why not in place for variables?
>
> Why everybody from us should define "GDB custom method" ?
>
>
> On 4/13/12 12:27 AM, "Dmitry Markman" <email@hidden> wrote:
>
>> define gdb custom method, that will use some
>> API that you should create
>>
>> that API will convert wchar_t to UTF8 and then just use gdb's print
>> it should work, because mac os x terminal understands utf8
>> hope it will help
>
>
> and
>
>> On 4/13/12 1:28 AM, "Sebastien Metrot" <email@hidden> wrote:
>
>> This problem was one of the reasons for moving all my code base from wchar_t*
>> to char* (and utf8). If your code really is unicode aware you will have to
>> handle many special cases where one codepoint!=one glyph/entity anyway
>> (diacritics, normalization, etc). Enumerating unicode code points in an utf8
>> string is easy to implement and it forces you to really think about semantics
>> of what you want to do with the text.
>> And it displays nicely in the debugger, even as an std::string ;-).
>>
>> S.
>>
>>
>> --
>> Sebastien Metrot
>> Yasound - CTO - Cofounder
>> email@hidden
>>
>>
>>
>>
>> On Apr 12, 2012, at 10:03 PM, Ruslan Zasukhin wrote:
>>
>>> Hi C++ developers,
>>>
>>> Using 4.3.2 XCODE and even LLVM debugger
>>> We still was disappointed that debugger is not able show unicode strings.
>>>
>>> Actually even std::strings (wchar_t*) are not shown ...
>>>
>>> We need each time open memory browser to see Letters ...
>>>
>>>
>>> Any hint?
>>>
>>> How to live without this? :-)
>
> --
> Best regards,
>
> Ruslan Zasukhin
> VP Engineering and New Technology
> Paradigma Software, Inc
>
> Valentina - Joining Worlds of Information
> http://www.paradigmasoft.com
>
> [I feel the need: the need for speed]
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden