Lines Matching refs:emph

67 within a running program.  This is called \emph{local} unwinding.  Say
71 initialize an \emph{unwind~cursor} based on this snapshot.  This is
104 by definition, only the \emph{preserved} machine state can be accessed
106 \emph{callee-saved} (``preserved'') registers.  However, in some
108 \emph{caller-saved} (``scratch'') registers are preserved in the stack
178 arguments: a pointer to a set of \emph{accessor} routines and an
208 We call the machine that is running \Prog{libunwind} the \emph{host}
210 \emph{target}.  If the host and the target platform are the same, we
211 call it \emph{native} unwinding.  If they differ, we call it
212 \emph{cross-platform} unwinding.
244 use locking.  Such routines \emph{must~not} be called from signal
245 handlers (directly or indirectly) and are therefore \emph{not}
248 any routine that may be needed for \emph{local} unwinding is
250 signal-safe).  For remote-unwinding, \emph{none} of the
260 information for \emph{all} dynamically generated code because