List Info

Thread: QStrings are not displayed in debugger (KDevelop 3.4)




QStrings are not displayed in debugger (KDevelop 3.4)
user name
2006-08-18 16:16:34
Hi,

 I found that displaying QStrings from Qt4 in the debugger
is broken 
again. It shows that "there is no member named len.
QString" or 
something like that. Could somebody look what has happened?

Andras
-- 
Quanta Plus developer - http://quanta.kdewebdev.o
rg
K Desktop Environment - http://www.kde.org
_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel
QStrings are not displayed in debugger (KDevelop 3.4)
user name
2006-08-19 13:12:43
On Saturday 19 August 2006 02:16, Andras Mantia wrote:
> Hi,
>
>  I found that displaying QStrings from Qt4 in the
debugger is broken
> again. It shows that "there is no member named
len. QString" or
> something like that. Could somebody look what has
happened?

You need to specify qt4 in the project options... (for each
project).  Have 
you done that?

Cheers,
Hamish.
_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel
QStrings are not displayed in debugger (KDevelop 3.4)
user name
2006-08-19 18:53:02
On Saturday 19 August 2006 16:12, Hamish Rodda wrote:
> On Saturday 19 August 2006 02:16, Andras Mantia wrote:
> > Hi,
> >
> >  I found that displaying QStrings from Qt4 in the
debugger is
> > broken again. It shows that "there is no
member named len. QString"
> > or something like that. Could somebody look what
has happened?
>
> You need to specify qt4 in the project options... (for
each project).
>  Have you done that?

No, but where should I do it? I verified all the project
options and I 
couldn't find something like this. Only to use the Qt4
include style 
and to use the Qt4 autocompletion PCS.

Andras

-- 
Quanta Plus developer - http://quanta.kdewebdev.o
rg
K Desktop Environment - http://www.kde.org
_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel
QStrings are not displayed in debugger (KDevelop 3.4)
user name
2006-08-19 22:16:49
On 19.08.06 21:53:02, Andras Mantia wrote:
> On Saturday 19 August 2006 16:12, Hamish Rodda wrote:
> > On Saturday 19 August 2006 02:16, Andras Mantia
wrote:
> > > Hi,
> > >
> > >  I found that displaying QStrings from Qt4 in
the debugger is
> > > broken again. It shows that "there is
no member named len. QString"
> > > or something like that. Could somebody look
what has happened?
> >
> > You need to specify qt4 in the project options...
(for each project).
> >  Have you done that?
> 
> No, but where should I do it? I verified all the
project options and I 
> couldn't find something like this. Only to use the Qt4
include style 
> and to use the Qt4 autocompletion PCS.

Matt is refering to more recent 3.4 versions, i.e. after
beta2 tagging
(btw: Matt where's the release of beta2?).

Andreas

-- 
You never hesitate to tackle the most difficult problems.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel
QStrings are not displayed in debugger (KDevelop 3.4)
user name
2006-08-19 23:27:59
On 20.08.06 00:16:49, Andreas Pakulat wrote:
> On 19.08.06 21:53:02, Andras Mantia wrote:
> > On Saturday 19 August 2006 16:12, Hamish Rodda
wrote:
> > > On Saturday 19 August 2006 02:16, Andras
Mantia wrote:
> > > > Hi,
> > > >
> > > >  I found that displaying QStrings from
Qt4 in the debugger is
> > > > broken again. It shows that "there
is no member named len. QString"
> > > > or something like that. Could somebody
look what has happened?
> > >
> > > You need to specify qt4 in the project
options... (for each project).
> > >  Have you done that?
> > 
> > No, but where should I do it? I verified all the
project options and I 
> > couldn't find something like this. Only to use
the Qt4 include style 
> > and to use the Qt4 autocompletion PCS.
> 
> Matt is

That should read Hamish.

Andreas

-- 
You'll wish that you had done some of the hard things when
they were easier
to do.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel
QStrings are not displayed in debugger (KDevelop 3.4)
user name
2006-08-20 18:58:49
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.

Andras

-- 
Quanta Plus developer - http://quanta.kdewebdev.o
rg
K Desktop Environment - http://www.kde.org
_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel
QStrings are not displayed in debugger (KDevelop 3.4)
user name
2006-08-21 03:42:29
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...

Cheers,
Hamish.
_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel
QStrings are not displayed in debugger (KDevelop 3.4)
user name
2006-08-21 06:52:36


On 8/21/06, Hamish Rodda <kde.org">roddakde.org&gt; 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&quot;
> 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.&nbsp; 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.*?

- Volodya

 

Cheers,
Hamish.


_______________________________________________
KDevelop-devel mailing list
barney.cs.uni-potsdam.de">KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel




QStrings are not displayed in debugger (KDevelop 3.4)
user name
2006-08-21 06:52:36


On 8/21/06, Hamish Rodda <kde.org">roddakde.org&gt; 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&quot;
> 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.&nbsp; 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.*?

- Volodya

 

Cheers,
Hamish.


_______________________________________________
KDevelop-devel mailing list
barney.cs.uni-potsdam.de">KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel




QStrings are not displayed in debugger (KDevelop 3.4)
user name
2006-08-21 07:05:39
On Monday 21 August 2006 16:52, Vladimir Prus wrote:
> On 8/21/06, Hamish Rodda <roddakde.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?

Cheers,
Hamish.
_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel
[1-10] [11-14]

about | contact  Other archives ( Real Estate discussion Medical topics )