Lines Matching refs:That
73 to the current frame, that is, the stack frame that corresponds to the
77 uncover the entire call-chain that led to the activation of function
79 that there are more frames in the chain, zero indicates that the end
80 of the chain has been reached, and any negative value indicates that
86 that sometimes has to move ``down'' by one stack frame could maintain
92 back \Var{prev} to \Var{curr} whenever that is necessary. In the most
94 frame and that way it could move up and down the callframe-chain at
98 registers that were preserved for the current stack frame (as
103 \Func{unw\_set\_fpreg}() writes a floating-point register. Note that,
110 as well. The exact set of registers that can be accessed via the
112 registers that can be read on all platforms: the instruction pointer
129 tell libunwind that your program only needs local unwinding, then a
135 employ both local-only and generic unwinding. That is, whether or not
136 \Const{UNW\_LOCAL\_ONLY} is defined is a choice that each source-file
140 portion of \Prog{libunwind} that manages unwind-info for dynamically
172 one that is running \Prog{libunwind}. Remote unwinding is typically
176 address-space object for that process. This is achieved with the
179 integer that specifies the byte-order of the target process. The
187 \Func{unw\_init\_local}(), except that it takes an address-space
192 select, e.g., the thread within a process that is to be unwound.
195 unwinding works exactly like in the local case. That is, you can use
208 We call the machine that is running \Prog{libunwind} the \emph{host}
209 and the machine that is running the process being unwound the
223 limitation is that a single source file (compilation unit) can include
226 isolated in separate source files---a limitation that shouldn't be an
229 Note that, by definition, local unwinding is possible only for the
239 that multiple threads may use \Prog{libunwind} simulatenously.
248 any routine that may be needed for \emph{local} unwinding is
258 unwind through code that has been generated at runtime (e.g., by a
269 to facilitate sharing, such that similar procedures can share much of
309 program that does native (same platform) unwinding.
311 building a program that unwinds a program on platform \Var{PLAT}.
314 may need to be specified for programs that can unwind programs on
