Jump to content
Xtreme .Net Talk

Recommended Posts

Posted
If an error occurs in a procedure then the execution of the code looks up the call stack to find the first error handling procedure. That's fine. But when you're debugging, it would be better if execution just stopped at the error, so that you can see what's causing it. If your error is a long way down a chain it could be very hard to track down where exactly it's occurring. If there's no error handling, execution does stop at the error, so it's tempting to do away with error handling in your code. Is there any way to run your application in the debugger so that execution does stop at the error, in spite of their being error handling code applicable?
  • Leaders
Posted

Under the Debug menu go to "Exceptions..."

 

What exactly you see depends on what version of what language(s) you are using, but there should be a way to stop execution not only on all exceptions, but you can pick and choose which exceptions to break on.

[sIGPIC]e[/sIGPIC]

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...