Clarification on "asterisk" in Debugger > Modules #7496
-
What does it mean |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Ordinarily, you should not see an asterisk in that column. Ghidra tries to automatically take module address ranges reported by the debugger, say gdb, and apply the equivalent mapping to Ghidra's program databases. To apply a mapping, we create an entry in the trace's "static mappings" table. You can view this using Window → Debugger → Static Mappings. Each mapping specifies two ranges of equal length, one for the dynamic side, and one for the static side. If auto-mapping succeeds, then for any mapped module, the module's range will exactly match the dynamic range of the mapping. This is ideal. However, you can use that same Static Mappings window to manually map any range, and so it's possible a mapping will overlap with a module but not match its range exactly. If that's the case, the "Mapping" column in the Modules table will include the asterisk. |
Beta Was this translation helpful? Give feedback.
Ordinarily, you should not see an asterisk in that column. Ghidra tries to automatically take module address ranges reported by the debugger, say gdb, and apply the equivalent mapping to Ghidra's program databases. To apply a mapping, we create an entry in the trace's "static mappings" table. You can view this using Window → Debugger → Static Mappings. Each mapping specifies two ranges of equal length, one for the dynamic side, and one for the static side.
If auto-mapping succeeds, then for any mapped module, the module's range will exactly match the dynamic range of the mapping. This is ideal. However, you can use that same Static Mappings window to manually map any range, and so it's po…