Bug 563261 - sourceEnd incorrectly decoded from positions in ProblemReporter.dereferencingNullableExpression
Summary: sourceEnd incorrectly decoded from positions in ProblemReporter.dereferencing...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.16   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-17 05:30 EDT by Stephan Wahlbrink CLA
Modified: 2024-04-28 18:53 EDT (History)
0 users

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 Stephan Wahlbrink CLA 2020-05-17 05:30:15 EDT 
In org.eclipse.jdt.internal.compiler.problem.ProblemReporter.dereferencingNullableExpression(long, LookupEnvironment) the sourceEnd position is incorrectly decoded from the start+end positions parameter. It is masked with 0xFFFF instead of 0xFFFFFFFF.
This causes wrongly placed "Potential null pointer access: this expression has a '@Nullable' type" reports in large source files.
Comment 1 Eclipse Genie CLA 2020-05-17 05:41:31 EDT 
New Gerrit change created: https://git.eclipse.org/r/163140
Comment 2 Eclipse Genie CLA 2022-05-08 17:53:05 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.
Comment 3 Eclipse Genie CLA 2024-04-28 18:53:02 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.