Bug 24334 - [breakpoints] Value to be...
Summary: [breakpoints] Value to be...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-02 16:13 EDT by Darin Wright CLA
Modified: 2007-05-24 16:48 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 Darin Wright CLA 2002-10-02 16:13:22 EDT 
The modification watchpoint event provides the "value to be" once the 
assignment is executed. We could provide access to the value in the inspector. 
Perhaps an action on the stack frame like "Inspect new value".
Comment 1 Darin Wright CLA 2002-10-02 16:13:36 EDT 
Marking as later.
Comment 2 Darin Wright CLA 2004-11-08 13:00:38 EST 
Open for 3.1
Comment 3 Darin Wright CLA 2004-12-11 11:38:53 EST 
Deferred again
Comment 4 Michael Rennie CLA 2007-05-23 10:31:02 EDT 
reopen to close
Comment 5 Michael Rennie CLA 2007-05-23 10:32:06 EDT 
marking as wontfix
Comment 6 Carsten Pfeiffer CLA 2007-05-23 11:00:43 EDT 
What's the reason for WONTFIXing it? Even if not available in the UI, the ability to inspect the new value can be quite useful for other debugging tools.

E.g. our debugger (for the Object Teams language, based on Java) has an "activation" feature, which enables or disables a module (kind of an aspect) at runtime. In order to track this activation we have a watch-point on the activation-flag and we need access to the new value in order to know the new activation state.
Comment 7 Darin Wright CLA 2007-05-24 16:48:39 EDT 
RE-opening to defer (again...)
Comment 8 Darin Wright CLA 2007-05-24 16:48:56 EDT 
Not planned for 3.3