Reporting Crashes in IMVU: Who threw that C++ exception?

We do something like this where i work. However, if a null or bad thread gets handled sometimes you get something uninformative, such as sem_wait() on top but doesn't really tell us where or what happened.

Good article, though!

Forgive my ignorance but why not wrap the fallback_algorithm() call in it's own try/catch throws a more explicit exception??

    try {
      this_might_fail();  
    } 
    catch (exception& e) {
      try {
        fallback_algorithm();  // throws ExceptionB
      }
      catch (ExceptionB& e) {
        report_crash();
      }
    }

Something I'm not getting here... Why not run the thing in a debugger?

E.g. dbx <executable> -> intercept -a -> run