On Feb 22, 12:42 pm, laxeraend <[email protected]> wrote: > On Feb 22, 10:34 am, John J Barton <[email protected]> > wrote: > > > > > If you mean: "break on an exception only when sometime in the future > > the exception is not trapped by a catch block", that is not possible. > > At the time the exception is thrown we don't know if it will be caught > > or not. > > I was thinking that maybe it would be possible to "look ahead" at the > stack at the time of the throw, anticipating whether it would be > caught or not. But it may not actually be needed, let's take the
Steve Fink from Mozilla pointed out that the JS engine can inspect the call stack and determine if any stack frame is in a try block. https://bugzilla.mozilla.org/show_bug.cgi?id=636057 Bug 636057 - implement jsdIStackFrame.getCatchingTryBlockFrame(exception) > unhandled part out, so what about breaking on a throw of specific > exception, restricted to a line/function/file? This should be enough, > because, if you restrict to type/message and location, you know that > it will be unhandled, having previously seen the error in the console. When you see the error message in the console, click on the link on the far right side. It takes you to the source line of the throw. Right click and enter a JS expression to restrict the breakpoint. jjb -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
