Broken displaying of QString's in the Variable view

[Vladimir Prus]

On Thursday 11 August 2005 15:43, Matt Rogers wrote:

> > After turning it off, I see the same "t\000e\000" thing. It was me who
> > broke it, by removing this code
> >
> >        // QT2.x string handling
> >        // A very bad hack alert!
> >        if (requested)
> >            return value.replace( QRegExp("\\\\000|\\\\0"), "" );
> >
> > I did not think it's relevant for Qt3. Hmm... it looks like putting this
> > back is not enough -- the above works fine for ASCII strings, but will
> > break for i18n strings. I'll look for a solution.
> >
> > As for references problem -- I see no value in r 440103 either, are you
> > sure it was working then?
> >
> > - Volodya
>
> perhaps something can be borrowed from the kde-devel-gdb file in
> kdesdk/scripts which handles things like printing QStrings and other
> various Qt data types.

I've just looked, and the code there masks off high byte. Guess I'd need to 
write QString value handling ;-) The current code already queries the right 
member of QString, I'd only need to convert the output of gdb to QString 
again.

- Volodya