Bug 563831 - Value for field while debugging is name specific not object
Summary: Value for field while debugging is name specific not object
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.13   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-02 11:37 EDT by vignesh velan CLA
Modified: 2022-06-24 18:11 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vignesh velan CLA 2020-06-02 11:37:21 EDT
While debugging if i am changing the value of field one in object A, it changes values of field one in all fields which named 'one' irrespective of object.

For examble,

   Class A{
Integer intA;
String one;

// getter and setter
}

Class B{
Integer intB;
String one;

// getter and setter
}

In Any class where i am accessing the values of A and B:
=========================================================
   A a = new A(1, "ValueOfB");
   B b = new B(2, "valueOfB"); 


If i change the value of one in A object, it changes value of one in B object as well while debugging,

Please fix the same or suggest me any latest version has this fix!

Thank you very much in the advance

Regards,
Vignesh velan S,
Comment 1 Rolf Theunissen CLA 2020-06-03 11:57:52 EDT
Moving to JDT.
Comment 2 Sarika Sinha CLA 2020-06-04 08:30:24 EDT
I am not able to reproduce this. Value in another object does not change. can you attach project and exact steps to reproduce?
Comment 3 Eclipse Genie CLA 2022-06-24 18:11:13 EDT
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.