Unicode, wxString, wxChar *, TCHAR *, QString etc.

[Vladimir Prus]

On Wednesday 19 April 2006 20:06, Alex Bligh wrote:
> I seem to be able to inspect "char *" variables in the watch window. I
> believe it's possible to inspect QString's as well.
>
> However, I can't seem to get kdevelop to inspect wchar *, TCHAR * (on a
> unicode build), or wxChar *, wxString (wxWidgets string primitives etc.).

Well, I plan to add support for wchar_t in future (well, let's say this year). 
The problem currently is whether I should be fixing gdb, or give up and 
handle this on KDevelop side.

>
> Now, I know it would be unrealistic to hope for an IDE which understood
> every possible string class, especially when the underlying debugger
> (gdb) appears deaf to unicode, but given I'm told kdevelop will
> examine a QString, is it possible to extend this functionality? I
> am told that the VC++ IDE has a text file which allows (if manually
> edited) wxString's to be supported much as it supports MFC CStrings.
> Is there (or should there be) similar functionality in kdevelop?

Did you read http://bugs.kde.org/show_bug.cgi?id=94313
The fundamental problem is not issuing some macro invocation. I can do this in 
current KDevelop in, ehmm, half-an-hour. The real problem is that if you 
have:

   int i;
   ........
   wxWstring foo;

then gdb will report 'foo' as live before it's constructor has executed, and 
so the macro author should be very carefull not to produce segfault when 
rendering the string. Gdb seems to be come unusable in that case.

Now, if you're:
   - Willing to write such macro
   - Willing to try development version of KDevelop

I think we can arrange for wxString to be displayed pretty soon.

- Volodya

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«