Exception Handling In Symbian C++

Actually, I think the RThread exception handling methods have been removed in v9.

No, it is moved to User::SetExceptionHandler

Hi CodePupil,
maybe you know Windows structured exception handling.
It is nearly the same here.

Use SetExceptionHandler with KExceptionInteger and
handle EExcIntegerDivideByZero in your ExceptionHandler()

This is not tested and not compiled, but maybe a good starting point. (I have currently no other sources)

void PupilsExcHandler(TExcType aExc)
{
  if(aExc == EExcIntegerDivideByZero)
  {
     return; // ignore   
     //User::Leave(KErrDivideByZero);
  }
  else
  {
     _LIT(KPanicCategory,"Exception");
     User::Panic(KPanicCategory, TExcType(aExc));
  }

}

As soon as possible in your current thread:

#ifdef EKA2
   User::SetExceptionHandler(PupilsExcHandler, KExceptionInteger);
#else
        RThread().SetExceptionHandler(PupilsExcHandler, KExceptionInteger);
#endif

Please note that panics are not the same as exceptions. You might have come to the same conclusion, however, I thought it was worth making it clear. So if your intent is to catch panics in general, then I tell you that an exception handler might not be the perfect tool for this. There are, however, some exceptions to this: a KERN-EXEC 3 panic can be fairly mapped to an EExcAccessViolation exception that your exception handler can catch.

It's worth noting that in case you want to catch each and every panic in your (single threaded) program, then you might want to run your code from within a separate thread so that when that thread exits for some reason (panics, for example) your main thread takes the control back and can evaluate the reason of exiting.

Cheers,

Tote

Well, I'm afraid this is such a "feature" that you have to live with. Unless you go for the separate thread solution I've just described below.

Also note that it's the last resort for the kernel to call a user-defined exception handler. Based on what you wrote it seems that the kernel has already shown the dialog by the time it calls your function.

Tote

The advantage of the thread solution is that it won't make your program collapse. So basically although the dialog is still shown your program continues to execute. That's sometimes very valuable, but I admit that it doesn't entirely solve your problem.

Tote