Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grouping the mapped memory in more meaningful way #36

Open
psjm3 opened this issue Mar 25, 2024 · 0 comments
Open

Grouping the mapped memory in more meaningful way #36

psjm3 opened this issue Mar 25, 2024 · 0 comments

Comments

@psjm3
Copy link
Contributor

psjm3 commented Mar 25, 2024

Currently chericat only knows about mappings that have a path, are marked as "grows down" (stack) or "guard", the rest are marked as "unknown". We could make use of the reservation to group the library boundaries, and then for the rest could be marked heuristically:

If it has a file mapping, use the path
If it has a 'D' sw mapping, label it as a stack
If it's a sw without a path or 'qu' (quarantined, pseudo-type), label it as a heap

For the visualisation each one of these types would be a separate node, then we can show the capability "relationship" between these well-defined types.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant