+<p>The runtime first attempts to find an <i>exception frame</i> corresponding to
+ the function where the exception was thrown. If the programming language
+ supports exception handling (e.g. C++), the exception frame contains a
+ reference to an exception table describing how to process the exception. If
+ the language does not support exception handling (e.g. C), or if the
+ exception needs to be forwarded to a prior activation, the exception frame
+ contains information about how to unwind the current activation and restore
+ the state of the prior activation. This process is repeated until the
+ exception is handled. If the exception is not handled and no activations
+ remain, then the application is terminated with an appropriate error
+ message.</p>
+
+<p>Because different programming languages have different behaviors when
+ handling exceptions, the exception handling ABI provides a mechanism for
+ supplying <i>personalities</i>. An exception handling personality is defined
+ by way of a <i>personality function</i> (e.g. <tt>__gxx_personality_v0</tt>
+ in C++), which receives the context of the exception, an <i>exception
+ structure</i> containing the exception object type and value, and a reference
+ to the exception table for the current function. The personality function
+ for the current compile unit is specified in a <i>common exception
+ frame</i>.</p>
+
+<p>The organization of an exception table is language dependent. For C++, an
+ exception table is organized as a series of code ranges defining what to do
+ if an exception occurs in that range. Typically, the information associated
+ with a range defines which types of exception objects (using C++ <i>type
+ info</i>) that are handled in that range, and an associated action that
+ should take place. Actions typically pass control to a <i>landing
+ pad</i>.</p>
+
+<p>A landing pad corresponds roughly to the code found in the <tt>catch</tt>
+ portion of a <tt>try</tt>/<tt>catch</tt> sequence. When execution resumes at
+ a landing pad, it receives an <i>exception structure</i> and a
+ <i>selector value</i> corresponding to the <i>type</i> of exception
+ thrown. The selector is then used to determine which <i>catch</i> should
+ actually process the exception.</p>
+
+</div>