Bug 357226 - Traditional memory view does not remove highlights from changed bytes when single stepping (using dsf)
Summary: Traditional memory view does not remove highlights from changed bytes when si...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-09 09:00 EDT by Phil Mason CLA
Modified: 2020-09-04 15:17 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Phil Mason CLA 2011-09-09 09:00:34 EDT 
Build Identifier: I20110613-1736

When single stepping through code that changes memory whilst examining it with a traditional memory view the changed bytes are highlighted but the highlight is never removed.

I think this is because handleDebugEvents in Rendering.java seems to only receive CHANGE events which don't update the memory cache.

Reproducible: Always

Steps to Reproduce:
1. Create a project that changes some memory.
2. Single step through the code that changes the memory with a traditional memory view open.
3. Changed bytes are highlighted in red but red bytes that not changed to black if a step doesn't update them.