#[repr(C)]pub struct blaze_cache_src_process {
pub type_size: usize,
pub pid: u32,
pub cache_vmas: bool,
pub reserved: [u8; 19],
}Expand description
Configuration for caching of process-level data.
Fields§
§type_size: usizeThe size of this object’s type.
Make sure to initialize it to sizeof(<type>). This member is used to
ensure compatibility in the presence of member additions.
pid: u32The referenced process’ ID.
cache_vmas: boolWhether to cache the process’ VMAs for later use.
Caching VMAs can be useful, because it conceptually enables the library to serve a symbolization request targeting a process even if said process has since exited the system.
Note that once VMAs have been cached this way, the library will refrain from re-reading updated VMAs unless instructed to. Hence, if you have reason to believe that a process may have changed its memory regions (by loading a new shared object, for example), you would have to make another request to cache them yourself.
Note furthermore that if you cache VMAs to later symbolize
addresses after the original process has already exited, you
will have to opt-out of usage of /proc/<pid>/map_files/ as
part of the symbolization request. Refer to
blaze_symbolize_src_process::no_map_files.
reserved: [u8; 19]Unused member available for future expansion. Must be initialized to zero.