Lines Matching +full:non +full:- +full:caching

16 \-\- a (mostly) platform\-independent unwind API 
132 to get a snapshot of the CPU registers (machine\-state). Then you 
143 uncover the entire call\-chain that led to the activation of function 
169 frame and that way it could move up and down the callframe\-chain at 
179 reads a floating\-point register, 
183 writes a floating\-point register. Note that, 
187 \fIcallee\-saved\fP
190 \fIcaller\-saved\fP
208 useful for implementing non\-local gotos and the exception handling 
209 needed by some high\-level languages such as Java. Resuming execution 
226 employ both local\-only and generic unwinding. That is, whether or not 
228 is defined is a choice that each source\-file 
229 (compilation\-unit) can make on its own. Independent of the setting(s) 
232 the program (normally \fB\-l\fPunwind).
235 that manages unwind\-info for dynamically 
271 used by debuggers and instruction\-set simulators, for example. 
274 address\-space object for that process. This is achieved with the 
279 integer that specifies the byte\-order of the target process. The 
290 except that it takes an address\-space 
301 to move ``up\&'' in the call\-chain, read and write 
305 .SH CROSS\-PLATFORM AND MULTI\-PLATFORM UNWINDING
322 \fIcross\-platform\fP
325 The principle behind supporting native, cross\-platform, and 
326 multi\-platform unwinding is very simple: for native unwinding, a 
329 \fB\-l\fPunwind\&.
330 For cross\-platform unwinding, a program 
331 includes <libunwind\-PLAT\&.h>
333 switch \fB\-l\fPunwind\-PLAT,
337 for IA\-64, hppa\-elf
338 for ELF\-based HP PA\-RISC, or x86
339 for 80386). Multi\-platform 
340 unwinding works exactly like cross\-platform unwinding, the only 
344 platform\-specific support for each supported target needs to be 
345 isolated in separate source files\-\-\-a limitation that shouldn\&'t be an 
351 targeting a cross\-platform will result in a link\-time error 
354 .SH THREAD\- AND SIGNAL\-SAFETY
358 routines are thread\-safe. What this means is 
364 To ensure thread\-safety, some libunwind
369 signal\-safe. The manual page for each libunwind
371 identifies whether or not it is signal\-safe, but as a general rule, 
374 signal\-safe (e.g., unw_step()
376 signal\-safe). For remote\-unwinding, \fInone\fP
379 routines are guaranteed to be signal\-safe. 
390 just\-in\-time (JIT) compiler). It is important to register the 
394 high\-level language exception handling may not work as expected. 
398 performance impact on JIT\-compilers. In particular, both routines are 
400 data\-structure encapsulating the dynamic unwind info has been designed 
406 generated code, see libunwind\-dynamic(3)\&.
408 .SH CACHING OF UNWIND INFO
430 select the exact caching policy in use for a given address\-space 
433 it is possible to turn off caching 
435 (at the cost of slower execution). By default, caching is enabled for 
448 libunwind\-PLAT\&.h
452 an IA\-64 program, the header file libunwind\-ia64.h
456 \fB\-l\fPunwind
457  Linker\-switch to add when building a 
460 \fB\-l\fPunwind\-PLAT
461  Linker\-switch to add when 
463 For example, to (cross\-)unwind an IA\-64 program, the linker switch 
464 \-lunwind\-ia64
472 libunwind\-dynamic(3),
473 libunwind\-ia64(3),
474 libunwind\-ptrace(3),
475 libunwind\-setjmp(3),
503 David Mosberger\-Tang