Is it possible to find out which lines of source code were executed?

Question

I am debugging C / C ++ code using Visual Studio. There is a loop called 10,000 times, and in one of the interactions, at the end of the loop, an error occurs because the program is trying to access the value N + 1 of an array of length N. I want to go back and debug the origin of the error, and I wonder if Visual Studio in debug mode to visually display or say which lines of source code were executed. Then it would be easier to find a mistake. Does anyone know if this is possible?

If this is not possible for VS, what other approaches can do this?

thank

EDIT: I also wonder if this can be done with any other IDE (Eclipse, Xcode, command line, etc.).

Answer 1

put a conditional breakpoint where access to the array occurs. Thus, your program will be divided into N + 1st access, and you will have a full stack trace for work.

Answer 2

If you know how many iterations you have to do (in this case 10,000), you can insert the hit counter into the loop for n (one before the error), and then do the next iteration using Intellisense to give you information about what might cause Problems?

Do you have a code that we can see that can help us help?

Answer 3

intellitrace vs2010

http://msdn.microsoft.com/en-us/magazine/ee336126.aspx

Answer 4

- , .

if(somethingThatMightNotHappen) {
    printf("This happened.\n");
    ...
}

Answer 5

, VS Debugger .

. , N- ( N-1- - ) (, idx > 1000) .

Answer 6

Visual Studio, , , , .

, , , (, 10) . , , , , , , .

, , , , . :

• ,
• ,
• ,
• 1

( ) - .

Answer 7

unit test , . unit test, , . , .

, unit test ( ), " " " ". , , , .

Nifty, eh?

++ , ++, . , , . , " ". , .

Answer 8

! try, catch- .

Answer 9

, , ++, ScottGu .

I assume that you already know about this, but it sounds to me as if you are looking for the call stack tab in debug mode. You can use the scoring mode or conditional debugging mode in a loop, and when an error occurs, you return down the call stack from where the data came from and set some breakpoints. Then you can run your program again and check how the data is created.