Break Into Debugger

[Data Danger]

Every now and then my program comes up with a unhandled exception win32 error and the program will be closed. I have Try/Catch statements in every routine and even in the Sub Main so the error should be caught there at least.

 

Also the error sometimes appear about five minutes after the screen has been left, I go and make a cup of tea and I come back and the error is being shown on the screen. :eek:

 

I have just changed the default setting in Exceptions to Break into debugger instead of continue and when I run the program exceptions are being displayed that are not picked up by the Try/Catch statements. The errors are coming from the Infragistics UltraWinGrid control. Does anybody know why this is happening ? and could this be the reason why my program will show the ***.exe will now close.

 

Thanks for your time

[IngisKahn]

My guess would be to ask Infragistics about thier UltraWinGrid.

[Data Danger]

I have done that and I'm awaiting a reply. I was hoping for a more positive reply than that, not just about infragistics but in general. Should the above happen regardless of the third party controls being used? Should exceptions be skipped over with controls that you cannot break into? Should you always leave break into debugger on while programming and switch it off when doing a release?

 

While using break into debugger I have found several third party controls that throw exceptions that are not caught by the Try/Catch statement but do not seem to harm the program why?

 

Look forward to some more postive replies.

 

Thanks for your time.

[PlausiblyDamp]

You can sometimes get problems if the problem is raised on a different thread to the one your Try ... Catch block is on; don't have MSDN / VS.Net installed on this PC at the moment but This and this may offer some pointers on catching all unhandled errors.

If the errors raised by the grid are not causing problems then I wouldn't worry - it could be a case that the grid itself is catching and dealing with the errors anyway.

[Data Danger]

Thanks for a positive reply. Previously before this post I had inserted a global error handler and it did not catch the reported errors. I also have a Try/Catch in the Sub Main this catches unhandled errors as well.

 

I will just keep on trying different things for now.

[Data Danger]

PlausiblyDamp <If the errors raised by the grid are not causing problems then I wouldn't worry >

 

I'm not sure what is causing the program to stop. The log message is

 

Faulting application tester.exe, version 5.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x4de7640a.

 

I don't know what this means. I only set break into debugger to see if I could trap what was causing the above to happen. That's when I came across other third party objects causing untrappable exceptions. Was it these controls terminating my program. The error does not appear at a logical time has I mentioned I could have been using my program left the screen with no problems gone to make a cup of tea come back and the error is on the screen. How would I trap this type of error?

 

Thanks for your time.