| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit 72fcf44f3731ade3cf1310da55f633f1cb9069ce.
|
|
|
|
|
|
|
|
|
|
|
|
through the Container Browser dialog.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
map, searches, and tag types
|
|
|
|
python callers listing referenced calls
Fixes https://github.com/Vector35/binaryninja-api/issues/7308
|
|
|
|
XNU maps kernel cache segments in with different permissions than the
load commands indicate. For instance, `__DATA_CONST` is initially mapped
as read-write before later being re-mapped as read-only. Treating it as
read-only results in analysis falsely assuming that global variables
cannot change.
To work around this we maintain a mapping from segment name to initial
permissions (i.e., most lax permissions) and favor them over permissions
derived from the segment load command. Section semantics are also
derived from the segment's permissions when the segment is present in
the mapping.
The mapping is based on the initial permissions established by
`arm_vm_prot_init` within the XNU source.
|
|
This returns a raw FFI handle and should only be used internally or in special FFI handling code
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also adds support for parsing bitfields in PDB, DWARF and SVD plugins
WIP: API needs to be considered more, also need to find type related apis that may need to be rethought.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
