Bug 261783 - WatchpointTrigger events don't show the watchpoint's expression
Summary: WatchpointTrigger events don't show the watchpoint's expression
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-21 05:20 EST by mihaib CLA
Modified: 2020-09-04 15:19 EDT (History)
2 users (show)

See Also:

Attachments
Proposed fix. (3.56 KB, patch)
2009-01-22 10:17 EST, mihaib CLA 		no flags Details | Diff
View All 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 mihaib CLA 2009-01-21 05:20:02 EST 
When a watchpoint is hit and the thread status is updated with an explanation, the ICDIWatchpointTrigger interface doesn't provide the specific expression associated with the triggered watchpoint.
Comment 1 mihaib CLA 2009-01-22 10:17:41 EST 
Created attachment 123380 [details]
Proposed fix.

The proposed fix changes the parametrized string displayed for ICDIWatchpointTrigger event by adding a new parameter - the watchpoint's expression. The expression's value is obtained via the ICDIWatchpointTrigger::getWatchpoint().getWatchExpression().
Comment 2 John Cortell CLA 2009-01-27 18:55:59 EST 
Unfortunately, it doesn't look like watchpoints are working in our gdb/mi/CDI support...at least not with cygwin. Need to be able to hit a watchpoint in order to test this fix.