23
Comments
  • 17
    Don’t you need to step down one more time to view it?
  • 2
    @devTea it crashes at the next step, so I can’t verify this
  • 4
    @JS96 try catch every method under that, good luck
  • 5
    Put your breakpoint *on* either the opening brace of the catch scope or the writeline statement.

    You’re breaking on the top part of the catch, before it’s been bound to your ex identifier.
  • 3
    Already fixed guys, but thanks!
  • 2
    @JS96 don’t be that guy, what was it in the end?
  • 5
    @Brolls
    *topic archived 7 years ago*
  • 1
    Check exception for null before output
  • 3
    The problem here was the fact that the software crashed at the "catch", not before or after, so it didn't even put the exception to the "ex" object.

    I found that the problem was in another module, but it was still a really strange behavior of the Visual Studio debugger.
Add Comment