| 1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192 |
- '\" t
- .\" Manual page created with latex2man on Thu Aug 16 09:44:44 MDT 2007
- .\" NOTE: This file is generated, DO NOT EDIT.
- .de Vb
- .ft CW
- .nf
- ..
- .de Ve
- .ft R
- .fi
- ..
- .TH "UNW\\_FLUSH\\_CACHE" "3" "16 August 2007" "Programming Library " "Programming Library "
- .SH NAME
- unw_flush_cache
- \-\- flush cached info
- .PP
- .SH SYNOPSIS
- .PP
- #include <libunwind.h>
- .br
- .PP
- void
- unw_flush_cache(unw_addr_space_t
- as,
- unw_word_t
- lo,
- unw_word_t
- hi);
- .br
- .PP
- .SH DESCRIPTION
- .PP
- The unw_flush_cache()
- routine flushes all cached info as it
- relates to address\-range lo
- to hi
- (non\-inclusive) in the
- target address\-space as\&.
- In addition, all info cached for
- address\-space as
- that is not tied to a particular code\-range is
- also flushed. For example, the address of the dynamic registration
- list is not tied to a code\-range and its cached value (if any) is
- flushed by a call to this routine. The address range specified by
- lo
- and hi
- should be understood as a hint:
- unw_flush_cache()
- may flush more information than requested,
- but \fInever\fP
- less. In other words, unw_flush_cache()
- may
- overflush, but not underflush.
- .PP
- As a special case, if arguments lo
- and hi
- are both 0, all
- information cached on behalf of address space as
- is flushed.
- .PP
- .SH RETURN VALUE
- .PP
- The unw_flush_cache()
- routine cannot fail and does not
- return a value.
- .PP
- .SH THREAD AND SIGNAL SAFETY
- .PP
- The unw_flush_cache()
- routine is thread\-safe as well as safe to
- use from a signal handler.
- .PP
- .SH SEE ALSO
- .PP
- libunwind(3),
- unw_set_caching_policy(3)
- .PP
- .SH AUTHOR
- .PP
- David Mosberger\-Tang
- .br
- Email: \fBdmosberger@gmail.com\fP
- .br
- WWW: \fBhttp://www.nongnu.org/libunwind/\fP\&.
- .\" NOTE: This file is generated, DO NOT EDIT.
|
