Debugging classes with DOM::Node
Andras Mantia
amantia at kde.org
Mon Nov 10 19:26:58 GMT 2003
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 10 November 2003 20:44, Dirk Mueller wrote:
> On Monday 10 November 2003 16:41, Andras Mantia wrote:
>
> I don't think this was relevant for kde-core-devel, moving to a more
> appropriate list..
As you wish. :-)
>
> > patience to see how long does it take), as it prints recursively the
> > content of those members:
>
> sure, it prints the whole tree, since it recursively tries to print all
> members.
I'm not sure I understand this. The object I try to print looks like:
class Node {
Node *parent;
Node *next;
Node *prev;
Node *child;
...
DOM::Node _rootNode;
DOM::Node _leafNode;
}
If the DOM::Node is not there, printing is OK, it does not try to recursively
print the parent, next, prev, child. Hm, I just have a though. Would it help
if we use a DOM::Node pointer there? Sure that would be slower, but I need to
see the content of a Node in so many cases that it might worth to do that
way.
> There might be an option for gdb to disable this behaviour.
I've tried to find something, but without success until now.
> I do
> not know it. an easier way would be to just access the member you're
> interested in.
Yes, it's easier if you do from the gdb prompt, but a little harder if you
wish to enjoy debugging in KDevelop.
- --
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
iD8DBQE/r+aCTQdfac6L/08RAt6cAKDoKIILEzggcepy93/VuMRtJztmxQCdHaJX
lb2uv3qkKVoJqrZ1OqFTWTM=
=PtTv
-----END PGP SIGNATURE-----
More information about the kfm-devel
mailing list