diff options
| author | Dimitry Andric <dim@FreeBSD.org> | 2016-07-23 20:44:14 +0000 |
|---|---|---|
| committer | Dimitry Andric <dim@FreeBSD.org> | 2016-07-23 20:44:14 +0000 |
| commit | 2b6b257f4e5503a7a2675bdb8735693db769f75c (patch) | |
| tree | e85e046ae7003fe3bcc8b5454cd0fa3f7407b470 /docs/SafeStack.rst | |
| parent | b4348ed0b7e90c0831b925fbee00b5f179a99796 (diff) | |
Notes
Diffstat (limited to 'docs/SafeStack.rst')
| -rw-r--r-- | docs/SafeStack.rst | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/SafeStack.rst b/docs/SafeStack.rst index 21e9b6c621a8..f01b75f5cb37 100644 --- a/docs/SafeStack.rst +++ b/docs/SafeStack.rst @@ -178,6 +178,17 @@ Please refer to the `Code-Pointer Integrity <http://dslab.epfl.ch/proj/cpi/>`__ project page for more information about the design of the SafeStack and its related technologies. +setjmp and exception handling +----------------------------- + +The `OSDI'14 paper <http://dslab.epfl.ch/pubs/cpi.pdf>`_ mentions that +on Linux the instrumentation pass finds calls to setjmp or functions that +may throw an exception, and inserts required instrumentation at their call +sites. Specifically, the instrumentation pass saves the shadow stack pointer +on the safe stack before the call site, and restores it either after the +call to setjmp or after an exception has been caught. This is implemented +in the function ``SafeStack::createStackRestorePoints``. + Publications ------------ |