Bugzilla – Bug 316258
try/catch/finally notifications
Last modified: 2007-09-15 21:24:34 UTC
---- Reported by toshok@ximian.com 2004-10-18 15:02:51 MST ---- 1) if you're stepping through a try {} block and step over a statement that causes an exception to be thrown, execution continues as if you'd typed "continue", even if there's a catch {} block that matches. 2) if you step out of a try {} block which has a finally {] block, execution continues until the first statement *after* the finally {} block. <lupus> there should be an interface that the jit uses to communicate to the debugger when an exception gets thrown and when it passes the control to a catch/finally clause <lupus> when the debugger gets the notification it will set the breakpoint to the beginning of the catch ---- Additional Comments From martin@ximian.com 2004-10-20 12:37:01 MST ---- The notification mechanism is now in CVS, and it works fine when single-stepping. What still needs to be added is some logic on when to stop in the catch/finally and when not and then some filters. ---- Additional Comments From toshok@ximian.com 2004-10-31 01:07:08 MST ---- martin added this functionality during the summit. marking fixed. Unknown operating system unknown. Setting to default OS "Other".