On Feb 21, 11:17 pm, laxeraend <[email protected]> wrote: > This appears to create a normal breakpoint, triggered by the location, > irrespective of whether an unhandled exception is thrown. There are > situations when an app is unusable because such breakpoints are hit so > frequently, and you simply don't care about 99.99% of such events, > whereas the throwing of an unhandled exception is very significant and > the only time you want to stop. What I am requesting is a breakpoint > that's triggered by the throwing of a specific unhandled exception, > not simply arriving at a given line of code. Such a breakpoint need > not even be specific to a location, although the ability to restrict > it to a line/function/file would also be helpful. What do you think?
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. We do have a new technique for capturing information that we may be able to apply to this case. It would not be a breakpoint (since that is impossible) but a 'querypoint', a snapshot that looks like a breakpoint but the program is not halted there. If you have something else in mind let us know. 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.
