| Summary: | [evaluation] NPE from watch expression | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Darin Wright <darin.eclipse> | ||||
| Component: | Debug | Assignee: | Michael Rennie <Michael_Rennie> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P2 | CC: | daniel_megert, ekuleshov, geziefer, hauser, maxime_daniel, somanchi | ||||
| Version: | 3.2 | ||||||
| Target Milestone: | 3.2.1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Darin Wright
*** Bug 105169 has been marked as a duplicate of this bug. *** for some reason the method binding being passed in is null....this one will take alot more effort and digging than allowed for the remainder or the RC's. I'll take a look at this one... I've got some ideas. Seems to be caused by the fact the fName is a private field access that is not visible from the receiving object that the expression is compiled in. Same problem existed in 3.1. Marking as later as this is not a regression. The best fix would be to propogate the compilation error to the user - i.e. fName is not visible. *** Bug 140637 has been marked as a duplicate of this bug. *** Marking as 3.3 Investigate for 3.2.1 Created attachment 43794 [details]
patch
Patch reports the error to the user when unable to resolve a method binding.
Released to TARGET_321 branch Released to HEAD Released to R3_2_maintenance branch Please verify, Mike. verified *** Bug 151244 has been marked as a duplicate of this bug. *** *** Bug 154656 has been marked as a duplicate of this bug. *** see also Bug 277574 |