#[repr(C)]pub struct blaze_normalize_opts {
pub type_size: usize,
pub sorted_addrs: bool,
pub map_files: bool,
pub apk_to_elf: bool,
pub reserved: [u8; 21],
}Expand description
Options influencing the address normalization process.
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.
sorted_addrs: boolWhether or not addresses are sorted (in ascending order) already.
Normalization always happens on sorted addresses and if the addresses are sorted already, the library does not need to sort and later restore original ordering, speeding up the normalization process.
map_files: boolWhether to report /proc/<pid>/map_files/ entry paths or work
with symbolic paths mentioned in /proc/<pid>/maps instead.
Relying on map_files may make sense in cases where
symbolization happens on the local system and the reported paths
can be worked with directly. In most other cases where one wants
to attach meaning to symbolic paths on a remote system (e.g., by
using them for file look up) symbolic paths are probably the
better choice.
apk_to_elf: boolNormalize addresses inside APKs to the contained ELF file and
report a regular blaze_user_meta_kind::ELF meta data entry
instead of an blaze_user_meta_kind::APK one. As a result,
the reported file offset will also be relative to the contained
ELF file and not to the APK itself.
reserved: [u8; 21]Unused member available for future expansion. Must be initialized to zero.