yetangitu/ghidra
1
0
Fork 0
mirror of https://github.com/NationalSecurityAgency/ghidra.git synced 2025-10-04 18:29:37 +02:00
Code Issues Releases Wiki Activity

Merge remote-tracking branch 'origin/GP-3891_gdbWineLauncher--SQUASHED'

Browse source
This commit is contained in:
Ryan Kurtz 2024-03-07 09:15:44 -05:00
commit df29f50fa3
8 changed files with 255 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

25
Ghidra/Debug/Framework-TraceModeling/src/main/java/ghidra/trace/model/modules/TraceStaticMappingManager.java
View file

@ -26,11 +26,12 @@ import ghidra.trace.model.Lifespan;
/**
* Manages mappings from this trace into static images (Ghida {@link Program}s)
*
* Most commonly, this is used to map sections listed by a connected debugger to those same sections
* of programs already imported into the same Ghidra project. It is vitally important that the image
* loaded by the target is an exact copy of the image imported by Ghidra, or else things may not be
* aligned.
* <p>
* Most commonly, this is used to map modules listed by a connected debugger to programs already
* imported into the same Ghidra project. It is vitally important that the image loaded by the
* target is an exact copy of the image imported by Ghidra, or else things may not be aligned.
*
* <p>
* Note, to best handle mapping ranges to a variety of programs, and to validate the addition of new
* entries, it is unlikely a client should consume mapping entries directly. Instead, a service
* should track the mappings among all open traces and programs, permitting clients to mutate and
@ -42,6 +43,7 @@ public interface TraceStaticMappingManager {
/**
* Add a new mapping, if not already covered
*
* <p>
* A new mapping may overlap an existing mapping, so long as they agree in address shift.
* Furthermore, in such cases, the implementation may coalesce mappings to remove duplication.
*
@ -50,7 +52,7 @@ public interface TraceStaticMappingManager {
* @param toProgramURL the (Ghidra) URL of the static image ("to")
* @param toAddress the starting address (in string form) in the static image ("to")
* @throws TraceConflictedMappingException if an existing mapping conflicts. See
* {@link #isAnyConflicting(AddressRange, Lifespan, URL, String)}
* {@link #findAnyConflicting(AddressRange, Lifespan, URL, String)}
* @return the new entry, or any entry which subsumes the specified mapping
*/
TraceStaticMapping add(AddressRange range, Lifespan lifespan, URL toProgramURL,
@ -75,14 +77,16 @@ public interface TraceStaticMappingManager {
/**
* Check if another mapping would conflict with the given prospective mapping
*
* <p>
* Mappings are allowed to overlap, but they must agree on the destination program and address
* throughout all overlapping portions.
*
* TODO: It'd be nice if the manager automatically merged overlapping mappings in agreement or
* provided a "deduplicate" method which optimized the entries in the database. This gets
* complicated, since we're dealing with overlapping rectangles, not strict one-dimensional
* ranges. Look into existing research for optimizing coverage of shapes by rectangles. The same
* is needed for property maps in 2 dimensions.
* <p>
* <b>TODO</b>: It'd be nice if the manager automatically merged overlapping mappings in
* agreement or provided a "de-duplicate" method which optimized the entries in the database.
* This gets complicated, since we're dealing with overlapping rectangles, not strict
* one-dimensional ranges. Look into existing research for optimizing coverage of shapes by
* rectangles. The same is needed for property maps in 2 dimensions.
*
* @param range the range in the trace ("from")
* @param lifespan the span of time in the trace
@ -96,6 +100,7 @@ public interface TraceStaticMappingManager {
/**
* Find all mappings which overlap the given adddress range and span of time
*
* <p>
* Note, this returns overlapping entries whether or not they conflict.
*
* @param range the range in the trace ("from")