CODEWITHSUNDEEP
c#visual-studiodebugging
Bohn
Bohn

Reputation: 26929

how to create a more accurate Break Point or Try/Catch

I have two FOR loops that the outer will repeat 64 times some where I know there is a index out of bound error How can I set a good break point or try/catch block,etc that exactly shows me the index and line of code that is causing the problem. ( C# WinApp)

Thanks all.

Upvotes: 1

Views: 628

Answers (3)

LBushkin
LBushkin

Reputation: 131806

In the VS debugger, you can just enable "Break On Thrown Exception" in the Exceptions dialog. Then you don't need to set a breakpoint, the debugger will automatically stop when the exception is raised.

You make this change in: Debug >> Exceptions >> Common Language Runtime Exceptions

Just check the appropriate exception in the "Thrown" column in the dialog:

alt text http://img248.imageshack.us/img248/5733/breakg.png

If you need to break before the exception is raised (let's say to inspect some volatile data), it's possible to set conditional breakpoints on a particular line that only breaks when some condition in your code is true. To do this, you can set a regular breakpoint and then right click on the red circle icon in the margin and select: [Condition...].

This brings up the conditional breakpoint dialog where you can write an expression that will cause the debugger to break when evaluated to true (or when some value changes). Breakpoint conditions can be a bit finicky, but if you stick to simple variables in your code it works well.

alt text http://img293.imageshack.us/img293/2921/break.png

Upvotes: 7

Anthony Pegram
Anthony Pegram

Reputation: 126982

[ I think the other answers are better for this particular problem, but I'm leaving this because of the scoping considerations. ]

For quick debugging, go inside the loop so your loop variable will still be in scope and populated.

int[] array = new int[10];

for (int i = 0; i < 20; i++)
{
    try
    {
        int temp = array[i];
    }
    catch (IndexOutOfRangeException ex)
    {
        // i is still in scope
    }
}

Upvotes: 2

JaredPar
JaredPar

Reputation: 755457

If you're using Visual Studio the simplest way is to just hit F5. The debugger will automatically break on exceptions thrown by your code which is not being caught.

This won't necessarily work if the exception is being caught elsewhere in your code. If that is the case you can enable break on exceptions by going to

  • Debug -> Exceptions
  • Check "User Thrown" for CLR exceptions
  • Hit F5

Upvotes: 2

Related Questions