how about this nice debug feature
http://www.hut.fi/~amushtaq/debugf1.png
this way, after a break point the programmer can actually see the flow of the code, the if statements etc that were executed ?
or if there is such feature available in some IDE ??
-ds
-
-
... Interesting... Alternatively you could have it completely strip code that isn't executed so:
Code wrote:if(something == true)
{
doStuff();
}
else
{
doNOTdoStuff();
}
becomes simply:
Code wrote:{ doStuff(); } -
Code coverage tools sort of do this, but only show the results after the code has run.
I haven't seen code coverage running 'live' in a debugging session yet, but is looks like a good idea to me.
I vote for this one, if anyone from the VS team is looking
-
It would require a special "heavy debug" target in the compiler because additional code would have to be generated - normal debug info isn't enough to determine which code paths were taken in the procedure ahead of a breakpoint being hit. You need a add a set of flags to the stack-frame and then add instructions that set them when branches are taken (or clear them if they're not). That's more or less what code-coverage tools do.
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.