mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-29 19:45:01 +02:00
82b74d3cb6
When an address is resolved from an expression, the resulting address may carry a memory space provided by the backend to associate this address to a particular memory space. The current interface for the memory space service (e.g. IMemorySpaces2) can be used to parse the memory space contained in the expression. This update adds: 1) A new API method to resolve the memory space of an IExpressionDMAddress instance 2) The use of the memory space service to attempt to resolve the memory space. Note: if there is no memory space service, the memory space defaults to an empty string, which does not affect the default behaviour i.e. when memory spaces are not used. Change-Id: Idfe5669b26f84ee4e3e78f96f229ced75e6ec5c3 |
||
|---|---|---|
| .. | ||
| org.eclipse.cdt.dsf.gdb | ||
| org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui | ||
| org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui.tests | ||
| org.eclipse.cdt.dsf.gdb.tests | ||
| org.eclipse.cdt.dsf.gdb.ui | ||
| org.eclipse.cdt.examples.dsf.gdb | ||
| org.eclipse.cdt.gnu.dsf-feature | ||
| org.eclipse.cdt.gnu.dsf.source-feature | ||
| org.eclipse.cdt.gnu.multicorevisualizer-feature | ||
| org.eclipse.cdt.tests.dsf.gdb | ||