diff options
| author | Dietmar Maurer <dietmar@mono-cvs.ximian.com> | 2003-05-22 20:04:53 +0400 |
|---|---|---|
| committer | Dietmar Maurer <dietmar@mono-cvs.ximian.com> | 2003-05-22 20:04:53 +0400 |
| commit | 9bc145b02b326b5aae985d4480966b5ee392f69c (patch) | |
| tree | 766a762cac4f5790858ee3e99c88ff288cea4ce9 /docs/exceptions | |
| parent | f4656c2d26bca23f3e3789d59c0a8374146dd68c (diff) | |
2003-05-22 Dietmar Maurer <dietmar@ximian.com>
* exceptions-x86.c (mono_arch_handle_exception): bug fix.
* more docu
svn path=/trunk/mono/; revision=14803
Diffstat (limited to 'docs/exceptions')
| -rw-r--r-- | docs/exceptions | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/exceptions b/docs/exceptions index d2d810ba7d0..ab76c0f97af 100644 --- a/docs/exceptions +++ b/docs/exceptions @@ -62,16 +62,15 @@ to the local variables of the enclosing method. Its is possible that instructions inside those handlers modify the stack pointer, thus we save the stack pointer at the start of the handler, and restore it at the end. We have to use a "call" instruction to execute such finally handlers. This makes it -also possible to execute them inside the stack unwinding code. Filters receives -the exception object in ECX. +also possible to execute them inside the stack unwinding code. The exception +object for filters is passed in a local variable (cfg->exvar). throw: we first save all regs into a sigcontext struct (we pass the exception object in register ECX), and then call the stack unwinding code. -catch handler: receives the exception object in ECX. They store that -object into a local variable, so that rethrow can access the object. - +catch handler: catch hanlders are always called from the stack unwinding +code. The exception object is passed in a local variable (cfg->exvar). gcc support for Exceptions ========================== |