Question

Probably staying late fixing a few bugs tonight, but maybe SO can help me out. Does anyone know if there’s a way to ‘track’ where some ignored exceptions are occurring?

Basically I’m finding some System.OverflowExceptions in System.Drawing which are causing some graphics to not get painted (red X box syndrome).

Problem is, I can only tell this from the Debug window, and can not for the life of me find where this is being thrown. I’m guessing the coder of where this is happening wrote a

try{ something } finally { blah }

or…

try {something } catch { //Blah blah blah }

If I’m SOL as far as that goes, maybe somebody might know what methods in System.Drawing may cause a StackOverflow excption…

Thanks!

Answer 1

You can configure the debugger to break on an exception even if it has been handled.

You can configure the behavior via Debug -> Exceptions…. In your specific case you should check Debug -> Exceptions… -> Common Language Runtime Exceptions -> System -> System.OverflowException:

_{(source: scatterbright.com)}