C++ catching all exceptions

by 
try{
    // ...
} catch (...) {
    // ...
}

will catch all C++ exceptions, but it should be considered bad design. You can use c++11’s new current_exception mechanism, but if you don’t have the ability to use c++11 (legacy code systems requiring a rewrite), then you have no named exception pointer to use to get a message or name. You may want to add separate catch clauses for the various exceptions you can catch, and only catch everything at the bottom to record an unexpected exception. E.g.:

try{
    // ...
} catch (const std::exception& ex) {
    // ...
} catch (const std::string& ex) {
    // ...
} catch (...) {
    // ...
}

More Related Contents:

  1. Possibilities to quit a function
  2. If you shouldn’t throw exceptions in a destructor, how do you handle errors in it?
  3. Does C++ support ‘finally’ blocks? (And what’s this ‘RAII’ I keep hearing about?)
  4. C++ display stack trace on exception
  5. Why will std::sort crash if the comparison function is not as operator
  6. Throwing exceptions from constructors
  7. Why should exceptions be used conservatively?
  8. Should I use an exception specifier in C++?
  9. GDB complaining about missing raise.c
  10. Why doesn’t C++ use std::nested_exception to allow throwing from destructor?
  11. Throw keyword in function’s signature
  12. How do exceptions work (behind the scenes) in c++
  13. Who deletes the memory allocated during a “new” operation which has exception in constructor?
  14. Difference between C++03 throw() specifier C++11 noexcept
  15. Why catch an exception as reference-to-const?
  16. c++ exception : throwing std::string
  17. C++: Safe to use longjmp and setjmp?
  18. C++ – Arguments for Exceptions over Return Codes
  19. Windows/C++: Is it possible to find the line of code where exception was thrown having “Exception Offset”
  20. Why are C++ STL iostreams not “exception friendly”?
  21. boost thread throwing exception “thread_resource_error: resource temporarily unavailable”
  22. Why destructor is not called on exception?
  23. Determining exception type after the exception is caught?
  24. Should I inherit from std::exception?
  25. Does throw inside a catch ellipsis (…) rethrow the original error in C++?
  26. Under what circumstances are C++ destructors not going to be called?
  27. Measuring exception handling overhead in C++
  28. New (std::nothrow) vs. New within a try/catch block
  29. Why is a segmentation fault not recoverable?
  30. Throwing C++ exceptions across DLL boundaries

Leave a Comment