diff options
author | mostang.com!davidm <mostang.com!davidm> | 2004-03-31 00:52:17 +0000 |
---|---|---|
committer | mostang.com!davidm <mostang.com!davidm> | 2004-03-31 00:52:17 +0000 |
commit | 37e20822f47c206cd6ae088cce218990ab26e660 (patch) | |
tree | d44c21e72fc3f320cebb920378879135abed171e /doc | |
parent | e0f02d4775d01de09c75bff19f0975698cbe45d8 (diff) | |
download | libunwind-37e20822f47c206cd6ae088cce218990ab26e660.tar.gz |
Add new Platform-specific Notes section and document that getcontext()
can be used in lieu of unw_getcontext() but not vice versa.
(Logical change 1.196)
Diffstat (limited to 'doc')
-rw-r--r-- | doc/unw_getcontext.tex | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/unw_getcontext.tex b/doc/unw_getcontext.tex index 3356deb7..823fcba7 100644 --- a/doc/unw_getcontext.tex +++ b/doc/unw_getcontext.tex @@ -26,6 +26,17 @@ stack-pointer, will be stored. This routine is normally implemented as a macro and applications should not attempt to take its address. +\section{Platform-specific Notes} + +On IA-64, \Type{unw\_context\_t} has a layout that is compatible with +that of \Type{ucontext\_t} and such structures can be initialized with +\Func{getcontext}() instead of \Func{unw\_getcontext}(). However, the +reverse is \emph{not} true and it is \emph{not} safe to use structures +initialized by \Func{unw\_getcontext()} in places where a structure +initialized by \Func{getcontext()} is expected. The reason for this +asymmetry is that \Func{unw\_getcontext()} is optimized for maximum +performance and does not, for example, save the signal mask. + \section{Return Value} On successful completion, \Func{unw\_getcontext}() returns 0. |