News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

debugging vectors

Started by killerbot, October 01, 2009, 06:17:09 PM

Previous topic - Next topic

oBFusCATed

Because we call "info locals" and "info args" which return the values ready to be put in the tree
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

killerbot

Quote from: oBFusCATed on October 03, 2009, 12:53:54 PM
Because we call "info locals" and "info args" which return the values ready to be put in the tree
And can we further post process them ?
For these kind of variables the use is nearly none, the only thing it shows the the user is a bad debug experience.
Are there short term possibilities to improve ?

oBFusCATed

I'm not sure about trunk, probably no.
In the debugger branch locals and function args are missing at all.

There I want to add multiple watch windows + maybe locals and functions args windows. But I'm not exactly sure how to handle this.

Also we need a way to parse:

struct A
{
     int a;
     string b;
     vector<int> c;
};

But implementing this will make stepping even slower...

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]