This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 154644 [details] screenshot to illustrate the issue Repro steps: class A { Object o; public void foo() { Object z = o; } } // in some other code A a = new A(); a.foo(); a) create an instance `i` of some class with some field null, b) create a breakpoint on `Object z = o;`, c) debug, hit the breakpoint, and hover over the field, d) instead of o.toString(), a.toString() is displayed on the tooltip. Screenshot attached. Note: this is *not* a duplicate of https://netbeans.org/bugzilla/show_bug.cgi?id=8801 (since that bug is ancient and has different appearance)
This issue is already fixed in dev builds.
Created attachment 154676 [details] Project which does neither reproduce the described problem in the latest trunk builds nor in 8.0.2 I am sorry but I can't reproduce the problem in both 8.0.2 and latest trunk build.
Product Version: NetBeans IDE Dev (Build 201507150001) Updates: Updates available Java: 1.8.0_51; Java HotSpot(TM) 64-Bit Server VM 25.51-b03 Runtime: Java(TM) SE Runtime Environment 1.8.0_51-b16 System: Linux version 3.13.0-37-generic running on amd64; UTF-8; cs_CZ (nb) Verified as fixed. In case you can reproduce this issue in current daily builds, don't hesitate to reopen the bug.
I 100% certainly *had* and still have this issue in 8.0.2, though honestly I haven't tried dailies yet. Still, my repro was kind of lacking - the very code I posted is just the idea of when I got the bug - in clean-room setting it *doesn't* show this behaviour, and it seems it's a kind of https://en.wikipedia.org/wiki/Heisenbug - it *does* occur regularly to me while debugging, and it was always when the variable was null. I'm not able to reproduce it consistently, and it occurs virtually only in non-trivial applications in non-trivial situations. Still, it *does* happen on 8.0.2 (I've had one yesterday on fully-up-to-date 8.0.2) - IMO the best course of action would be to find a clear repro case for 8.0.2, and then try it on dailies. I'm out of ideas for this one ATM, will try to figure a better repro (at least for 8.0.2) when I get my hands on some free time. If anyone can try finding one, I'd be most grateful.
I'm marking this as RESOLVED INCOMPLETE until a good test case is found for 8.0.2, showing the defect - as per Jiri Kovalsky, I think that without a test where we can safely say what causes the bug in 8.0.2, we can't be sure it won't happen in dailies.
Isn't this a duplicate of issue #252138?
*** This bug has been marked as a duplicate of bug 252138 ***
Verifying then.
(In reply to Martin Entlicher from comment #6) > Isn't this a duplicate of issue #252138? Yup. Good catch on that one - I missed it while looking for dupes, it obviously *is* the exact problem I had. I marked it as a dupe, hopefully it's already solved in nightlies.