QStrings are not displayed in debugger (KDevelop 3.4)
rodda at kde.org
Mon Aug 21 07:05:39 UTC 2006
On Monday 21 August 2006 16:52, Vladimir Prus wrote:
> On 8/21/06, Hamish Rodda <rodda at kde.org> wrote:
> > On Monday 21 August 2006 04:58, Andras Mantia wrote:
> > > On Sunday 20 August 2006 01:16, Andreas Pakulat wrote:
> > > > Matt is refering to more recent 3.4 versions, i.e. after beta2
> > > > tagging (btw: Matt where's the release of beta2?).
> > >
> > > Thanks, updating partly helped. QString appear correctly, but KUrl's
> > > not. For the scheme, username, password, host, path, etc. I get the
> > > "cannot resolve overloaded method `QUrl': no arguments supplied"
> > > message as value.
> > This is a known problem (at least I think Volodya knows about it). It's
> > because the gdb-mi way of accessing accepts the parent class type in the
> > identifier, but it would seem that the non-mi way doesn't. Not sure what
> > the
> > best fix is here...
> I probably remembered about this problem before I went on vacation, but
> don't remember now that I'm back, and my todo list
> is silent on this. Can you give a pointer to a thread where this was
> discussed? Which version of KUrl is this? That in KDE 3.*?
I'm not sure if it was discussed. Basically the problem is displaying
QStrings which exist in a parent class of an object.
eg., with KUrl (from kde4), which inherits from QUrl:
- the strings are stored in QUrl.d, ie. QUrl's d pointer
- the custom command to display a string asks for eg. myurl.QUrl.d.host
- gdb doesn't like QUrl being there
Does that clear it up?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the KDevelop-devel