Bug 513047 - Support for using new value of the field in the Watchpoint condition
Summary: Support for using new value of the field in the Watchpoint condition
Status: REOPENED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-03 05:41 EST by Sarika Sinha CLA
Modified: 2024-01-15 04:07 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sarika Sinha CLA 2017-03-03 05:41:19 EST
Taking the enhancement out of Bug 96719 comment 24

Ability to define a new local variable with a unique name for the new value, so that it can also be proposed by Content Assist, e.g. "field$".

Add additional info text "new value that will be assigned to field 'field'" to the Content Assist proposal, and the solution should be self-explanatory.

But this will be available only if RHS for field is already calculated before the watchpoint condition is hit. As the value calculation of RHS may not be always possible, it can not be available if RHS is not calculated.
Comment 1 Eclipse Genie CLA 2020-02-03 13:05:29 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Sarika Sinha CLA 2020-02-03 23:50:34 EST
Requirement is still valid!
Comment 3 Eclipse Genie CLA 2022-01-24 00:22:00 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2024-01-15 04:07:46 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.