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.
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.