Bug 309032: Need APIs to support memory pages (add ability for backend to indicate a memory space qualification is necessary)

1 files changed, 15 insertions, 4 deletions

diff --git a/dsf/org.eclipse.cdt.dsf/src/org/eclipse/cdt/dsf/debug/service/IMemorySpaces.java b/dsf/org.eclipse.cdt.dsf/src/org/eclipse/cdt/dsf/debug/service/IMemorySpaces.java
index e5396f814ce..79794457d91 100644
--- a/dsf/org.eclipse.cdt.dsf/src/org/eclipse/cdt/dsf/debug/service/IMemorySpaces.java
+++ b/dsf/org.eclipse.cdt.dsf/src/org/eclipse/cdt/dsf/debug/service/IMemorySpaces.java
@@ -68,12 +68,23 @@ public interface IMemorySpaces extends IDsfService{
 		String getMemorySpaceId();
 		String getExpression();
 	}
-	
+
 	/**
 	 * Provides the memory spaces available in the given context.
 	 * 
-	 * @param ctx a DM context
-     * @param rm the asynchronous data request monitor
+	 * @param ctx
+	 *            a DM context
+	 * @param rm
+	 *            the asynchronous data request monitor. Returns a collection of
+	 *            memory space IDs.
+	 */
+	void getMemorySpaces(IDMContext context, final DataRequestMonitor<String[]> rm);
+	
+	/**
+	 * Return true if creating a memory block with a null memory space ID is NOT
+	 * supported. Some debuggers may not have the ability to infer the memory
+	 * space from an expression, in which case the user should be forced to
+	 * select a memory space when being prompted for a memory location.
 	 */
-	void getMemorySpaces(IDMContext context, final DataRequestMonitor<String[]> rm);	
+	public boolean creatingBlockRequiresMemorySpaceID();
 }