v1.3.0 Release Preparations

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Change Log
 
+## 1.3.0
+- Implemented [#102](https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/issues/102): Allow to set data breakpoints in memory view via context menu. ([Haydar Metin](https://github.com/haydar-metin))
+  - Note: This feature currently has experimental status and needs to be enabled through the extension setting `memory-inspector.dataBreakpoints`.
+- Fixed [#165](https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/issues/165): "Show in Memory Inspector" context menu entry for Watch window. ([Morten Engelhardt Olsen](https://github.com/xoriath))
+- Fixed [#172](https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/issues/172): Cell updates + rendering not properly working ([Jens Reinecke](https://github.com/jreineckearm))
+- Fixed [#184](https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/issues/184): Unable to load back hex file dumped from address above 0x80000000 ([Stavros Kollias](https://github.com/StavrosKolliasArm))
+
 ## 1.2.0
 - Fixed [#112](https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/issues/112): Edit memory value can cause "line break" in row for "autofit" groups per row. ([Martin Fleck](https://github.com/martin-fleck-at))
 - Fixed [#120](https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/issues/120): Variable tracker evaluates variables using `evaluateName` if present. ([Hampus Adolfsson](https://github.com/HampusAdolfsson))

README.md

@@ -16,6 +16,7 @@ A Visual Studio Code extension that provides a powerful and configurable memory
 - **Lock Views**: Keep views static, unaffected by updates from the debug session.
 - **Periodic Refresh**: Automatically refresh the memory data.
 - **Multiple Debug Sessions**: Switch between multiple debug sessions using a dropdown in the memory view.
+- **Data Breakpoints** (Experimental): Set data breakpoints in the memory view.
 - And much more
 
 ## Getting Started
@@ -79,6 +80,19 @@ These settings can be adjusted individually for each Memory Inspector view or gl
 
 The Memory Inspector supports multiple debug sessions. If multiple debug sessions are active, a dropdown appears in the memory view which allows you to switch between them. This enables you to target different debug sessions in multiple windows, simultaneously.
 
+## Set Data Breakpoints
+
+The Memory Inspector allows to set data breakpoints from a memory view. The feature is experimental and must be enabled through the extension setting `memory-inspector.dataBreakpoints`. Also, the debug adapter must support the `DataBreakpointInfo` and `SetDataBreakpoints` requests.
+
+![Screenshot of the Memory Inspector](./media/memory-inspector-data-breakpoints-screenshot.png)
+
+1. Data Breakpoints are managed through the context menu of a memory cell. You can select between data breakpoints that halt program execution on memory read (`Read`), write (`Change`), or both (`Access`).
+2. Memory rows with one or more data breakpoints are marked with a red circle.
+3. Memory cells with a data breakpoint are marked with a red frame.
+
+**Important**:
+The Memory Inspector installs data breakpoints via the debug adapter like other built-in IDE views. However, technical limitations of the IDE prohibit adding them to the `BREAKPOINTS` view. Hence, such breakpoints must be removed again via the Memory Inspector context menu.
+
 ## Contributing
 
 We welcome contributions on [GitHub](https://github.com/eclipse-cdt-cloud/vscode-memory-inspector).

package.json

@@ -2,7 +2,7 @@
   "name": "memory-inspector",
   "displayName": "Memory Inspector",
   "description": "A powerful and configurable memory viewer that works with debug adapters",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "publisher": "eclipse-cdt",
   "author": "Rob Moran <rob.moran@arm.com>",
   "license": "EPL-2.0",