Debugging without a stack trace

[bgowland]

Iain - do you have an uncaught exception handler?

[imilne]

I don't no. I always figured if I added one it might override whatever global one had been set up by sub. But then there probably isn't one otherwise it would be catching this stuff. Unless it only works at the namespace level? I've given them a new build with more stuff try/catch wrapped, so it that doesn't track it down I'll give the uncaught stuff a blast.

Iain

[bgowland]

Iain - I think I saw you'd identified the problem but for further info on unhandled exceptions...

I checked and the UnhandledExceptionHandler applies to the current AppDomain.

I did a quick test with my nDroid Service code and logged AppDomain.CurrentDomain.toString() from the main service code as well as from my nDroidLib.dll helper library (which has a different namespace). In both cases it logged the name of the CurrentDomain as "nDroidService.exe".

You could try logging AppDomain.CurrentDomain.toString() from the System plugin but if it shows the name as "NextPVR.exe" then that implies a handler would catch any unhandled exceptions in the whole of NextPVR. In saying that though if you registered a handler when the plugin started and un-registered it when the user leaves the plugin then in theory it will only catch unhandled exceptions related to the plugin itself.

Cheers,
Brian

[imilne]

It shows as NextPVR.exe.

I'm not sure if registering on activate/deactivate handles stuff like Live TV being started (via F2) without leaving a plugin's screen. It's possible you'd still be active under those conditions, I'd need to check.

Although as this has been (hopefully) an exceptionally rare situation I don't think I'll add any more error handling. The bit that caused the problem is in a try/catch now, even though it never claimed to throw that exception.

Iain