Some thoughts on ways the hex editor would interact with an input stream and the debugger. I visualize this using a context sensitive menu in the hex editor as an entrypoint, where these are some of the operations that could be offered.
1. Add/Delete/Mask/Set * Individual bytes * Blocks of bytes 2. Copy/Paste bytes * Use system clipboard for interoperability 3. Find/Replace bytes * In a selection * Across entire file 4. Set breakpoints on bytes * Stops execution at related point in schema * Would require custom additions to DAP backend 5. Set run options on bytes * Debug-to this byte (and break) * Start from this byte (skipping previous) The idea with breakpoints and run operations is that they would behave as a normal breakpoint in code would. I don't know if this is functionality for the first pass of the editor, but it is definitely something to keep in mind while designing that first pass. What other operations could be supported?
