Whoever tells me how I can turn off stopping on exceptions during debugging on project basis (without manually going to the global IDE options and turn it off and remembering to turn it on later again of course) by exception type or creates some plugin, unit, whatever to achieve that, will be my hero!
Whoever tells me how I can turn off stopping on exceptions during debugging on project basis (without manually going to the global IDE options and turn it off and remembering to turn it on later again of course) by exception type or creates some plugin, unit, whatever to achieve that, will be my hero!
/sub
ReplyDeleteFWIW there is a tool button that toggles "Notify on language exceptions" since quite a long time.
ReplyDeleteUwe Schuster Which is a global IDE setting. I know about that, thanks. I want to control that option per project and exception type.
ReplyDeleteBackground: I have unit tests that I debug from time to time and I don't want to halt when it throws some exception that I check for in my test but only on those that are not expected.
I would vote for that.
ReplyDeleteStefan Glienke Your "without manually going to the global IDE options and turn it off..." was a bit misleading. With that background information the "feature request" makes sense. Unless someone shows up with an existing plugin someone will have to write a plugin. Writing it itself will for sure be trivial compared to the research in the IDE internals that needs to be done first. If debugging of multiple projects at the same is not required then globally toggling the settings when starting the debugger might work and otherwise not.
ReplyDeleteUwe Schuster I could even think of the usefulness of setting it from the code itself. So setting ExpectedException in DUnit will turn it off because hey I am expecting that so don't stop - but I guess that will be almost impossible (unless I can integrate that into TestInsight to send that information to the IDE, change the setting there .. but it still needs the first step to be done first)
ReplyDeleteStefan Glienke Do you know how a thread tells the debugger it's name? So settings ExpectedException from code should be possible in general, but well if that thread name stuff is deep somewhere in C debugger stuff then it is not very likely that it can be done without the source.
ReplyDeleteIt should be possible to write a plugin that did this. I wish one specific plugin of mine was far enough along I could release public information ;)
ReplyDeleteYou know about the source breakpoint option "Ignore subsquent exceptions" ?
ReplyDeletePointers:
ReplyDeleteDbkDebugOpts.TDbkDebugOptions.ShouldStopOnException
Win32Debug.TNativeThread.DoHandleNtfy1stChanceException
/sub
ReplyDeleteI believe I posted a similar question a few years ago on SO: http://stackoverflow.com/questions/4931771/using-dunit-from-the-delphi-ide-and-avoid-breakpoint-on-exceptions
ReplyDeleteJohn Riche Thankfully that situation you described there does not arise anymore because of TestInsight :p
ReplyDeleteAgree with David Millington someone should write a plugin. I actually looked for this in GExperts yesterday but unfortunately its not in there. The plugin should not only be on a projetc-by-project basis but allow you to toggle which exceptions exceptions to ignore.
ReplyDelete