Bug 579052 - Ability to put modification breakpoint on a local variable
Summary: Ability to put modification breakpoint on a local variable
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.23   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-02 06:35 EST by Vikas Chandra CLA
Modified: 2024-02-24 06:16 EST (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 Vikas Chandra CLA 2022-03-02 06:35:18 EST 
Many times we have a function like isValid or getElements or similar wherein a local variable is declared at the start ( like boolean valid = true or List<String> ele = new ArrayList<>() Post that based on various conditions that local field is populated/modified and finally returned from that function.

As a debugger, my objective is to see when that element is modified or updated ( to see if it is working as per expectation).

Similar to field watchpoint, there should be a way to see a modification breakpoint on these local variables.
Comment 1 Eclipse Genie CLA 2024-02-24 06:16: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.