Bug 414894 - [registers] Should register view values be cleared when resuming thread execution?
Summary: [registers] Should register view values be cleared when resuming thread execu...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: Next   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on: 323552
Blocks:
  Show dependency tree
 
Reported: 2013-08-12 13:26 EDT by Marc Dumais CLA
Modified: 2020-09-04 15:27 EDT (History)
3 users (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 Marc Dumais CLA 2013-08-12 13:26:24 EDT 
When debugging with the Registers view open, it could be argued that displaying the register values only makes sense when the corresponding thread is stopped.  

At the moment, any register value cached when a thread last stopped is still displayed when a thread execution is resumed.  The values are updated only when the thread stops again.  It might be better to clear the register values when a thread is resumed.
Comment 1 Marc Khouzam CLA 2013-08-12 13:44:42 EDT 
I don't think we should be displaying values if the thread in question is running: those values are no longer valid.
Comment 2 Alvaro Sanchez-Leon CLA 2013-09-24 22:01:40 EDT 
I agree, this was quite visible during the implementation of Bug 323552 to display register values at stack frame level, keeping the values while running was quite confusing as we wouldn't know for which frame those values were.

So the implementation of Bug 323552, clears the registers values when transitioning to the running state i.e. receiving the Resume event.

Added Bug 323552 as a dependency for this bug