Useful as fuck

Don’t you need to step down one more time to view it?

@devTea it crashes at the next step, so I can’t verify this

@JS96 try catch every method under that, good luck

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.

Already fixed guys, but thanks!

@JS96 don’t be that guy, what was it in the end?

@Brolls
*topic archived 7 years ago*

Check exception for null before output

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.