How is the C++ exception handling runtime implemented?

by

Implementations may differ, but there are some basic ideas that follow from requirements.

The exception object itself is an object created in one function, destroyed in a caller thereof. Hence, it’s typically not feasible to create the object on the stack. On the other hand, many exception objects are not very big. Ergo, one can create e.g a 32 byte buffer and overflow to heap if a bigger exception object is actually needed.

As for the actual transfer of control, two strategies exist. One is to record enough information in the stack itself to unwind the stack. This is basically a list of destructors to run and exception handlers that might catch the exception. When an exception happens, run back the stack executing those destructors until you find a matching catch.

The second strategy moves this information into tables outside the stack. Now, when an exception occurs, the call stack is used to find out which scopes are entered but not exited. Those are then looked up in the static tables to determine where the thrown exception will be handled, and which destructors run in between. This means there is less exception overhead on the stack; return addresses are needed anyway. The tables are extra data, but the compiler can put them in a demand-loaded segment of the program.

More Related Contents:

  1. warning C4018: '<' : signed/unsigned mismatch [closed]
  2. Exception Handling with pointer [closed]
  3. Possibilities to quit a function
  4. How to handle wrong data type input
  5. When should I really use noexcept?
  6. Object destruction in C++
  7. On which platforms does integer divide by zero trigger a floating point exception?
  8. How can I propagate exceptions between threads?
  9. How to get error message when ifstream open fails
  10. How to know the exact line of code where an exception has been caused?
  11. Throwing exceptions from constructors
  12. Why should exceptions be used conservatively?
  13. C++ catching all exceptions
  14. When and how should I use exception handling?
  15. Why catch an exception as reference-to-const?
  16. c++ exception : throwing std::string
  17. In what ways do C++ exceptions slow down code when there are no exceptions thown?
  18. Catching exceptions from a constructor’s initializer list
  19. What should I know about Structured Exceptions (SEH) in C++?
  20. Reset Cuda Context after exception
  21. Determining exception type after the exception is caught?
  22. More Elegant Exception Handling Than Multiple Catch Blocks? [duplicate]
  23. Throwing an exception from within a signal handler
  24. throw new std::exception vs throw std::exception
  25. What happens if a constructor throws an exception?
  26. C++ : handle resources if constructors may throw exceptions (Reference to FAQ 17.4]
  27. How to throw std::exceptions with variable messages?
  28. Asp.net mvc override OnException in base controller keeps propagating to Application_Error
  29. Why vector access operators are not specified as noexcept?
  30. New (std::nothrow) vs. New within a try/catch block

Leave a Comment