Bug 450221 - [jdt] NPE in ProblemReporter.conditionalArgumentsIncompatibleTypes
Summary: [jdt] NPE in ProblemReporter.conditionalArgumentsIncompatibleTypes
Status: UNCONFIRMED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: shankha banerjee CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-06 00:06 EST by EPP Error Reports CLA
Modified: 2014-12-16 10:59 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description EPP Error Reports CLA 2014-11-06 00:06:10 EST
Hello committers,

we received a new error report for Eclipse 4.4.0.I20140606-1215.


General Information:
    anonymous-id:         c39c1c6e-31e4-4b91-81ad-d4555c950b56
    eclipse-build-id:     4.4.0.I20140606-1215
    eclipse-product:      org.eclipse.epp.package.standard.product
    operating system:     Windows7 6.1.0 (x86_64) - win32
    java-runtime-version: 1.7.0_51-b13

The following plug-ins were present on the execution stack (*):
    1. org.eclipse.jdt_3.10.0.v20140925-0400


Error Status:

    code:                   2
    plugin:                 org.eclipse.core.resources_3.9.0.v20140514-1307
    message:                Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
    fingerprint:            5a2f9e65
    exception class:        java.lang.NullPointerException
    exception message:      -
    number of children:     0
    
    java.lang.NullPointerException: null
    at java.lang.String.<init>(null:-1)
    at org.eclipse.jdt.internal.compiler.problem.ProblemReporter.conditionalArgumentsIncompatibleTypes(ProblemReporter.java:1572)
    at org.eclipse.jdt.internal.compiler.ast.ConditionalExpression.resolveType(ConditionalExpression.java:651)
    at org.eclipse.jdt.internal.compiler.ast.BinaryExpression.resolveType(BinaryExpression.java:1802)
    at org.eclipse.jdt.internal.compiler.ast.BinaryExpression.resolveType(BinaryExpression.java:1799)
    at org.eclipse.jdt.internal.compiler.ast.CombinedBinaryExpression.resolveType(CombinedBinaryExpression.java:344)
    at org.eclipse.jdt.internal.compiler.ast.ReturnStatement.resolve(ReturnStatement.java:330)
    at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:619)
    at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:299)
    at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:529)
    at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1207)
    at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1317)
    at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:587)
    at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:771)
    at org.eclipse.jdt.internal.compiler.ProcessTaskManager.run(ProcessTaskManager.java:137)
    at java.lang.Thread.run(null:-1)
   

    

Messages, stacktraces, and nested status objects may be shortened. Please visit 
http://dev.eclipse.org/recommenders/committers/confess/0.5/reports/-
for the complete error log.


Some general information and guidelines about how to use this bug report:

1. Feel free to move this bug to your own product and components. Please note
   that this bug is only accessible to Eclipse committers. If you move this bug
   please make sure that it's still in the "Security Advisor" group.

2. The bug contents of the fields status, resolution, keywords, and whitelist
   are presented to reporters. If you needs more information, please set the
   keyword "needinfo". This will trigger a specialized dialog asking the user
   to provide further details.

3. Use the following resolutions for the following situations:
   * CLOSED / FIXED: This bug has been fixed. Please provide additional
     information in the whiteboard field.
   * CLOSED / WORKSFORME: Use this resolution if you can't reproduce this issue
     and request further information. Please use the whiteboard text to specify
     more details what a user should provide and how.
   * CLOSED / INVALID: Use this resolution if the reported problem is a
     'user-configuration' problem. Please consider giving hints how to fix
     these issues in the whiteboard field.
   * CLOSED / NOT ECLIPSE: Use this if the problem is caused by another plugin
     not developed at Eclipse.org
   * CLOSED / MOVED: If this bug has been moved else where. Please provide more 
     information (e.g. a link) in the whiteboard field.

4. Please remember that only committers can view and comment on this bug. You
   may, however, manually add the reporting user to the bug's cc list. But keep
   in mind that the report may contains sensitive information.

5. If you are missing a feature, please file a enhancement request here:
   https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Recommenders.Incubator&component=Stacktraces
    
 

Thank you for your assistance.
Your friendly error-reports-inbox.


--
* Note: The list of present bundles and their respective versions was
  calculated by package naming heuristics. This may or may not reflect reality.
Comment 1 EPP Error Reports CLA 2014-11-06 00:06:11 EST
I've looked up the (to date) top-3 most similar bug groups and listed the 
closest bug of each group below. This report may or may not be duplicate of
those (low or similar scores for all entries may indicate that this hasn't
been reported yet):

>     1. Bug 445257: Errors occurred during the build. (err_grp: e4e17173) – 0,9    
>     2. Bug 448378: [jdt] Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". – 0,9    
>     3. Bug 448379: [compiler] NPE logged in TeamAnchor.getBestNameFromStat – 0,9    


If this report actually is a duplicate of those, please mark it as such. This
information helps me to improve the recommendations further for the next issue.

Thank you for your assistance.
Your friendly error-reports-inbox.
Comment 2 Marcel Bruch CLA 2014-12-10 08:04:02 EST
Not sure how an appropriate action looks like here. But I thought you may wanna know about this error. Please close it as invalid or worksforme if inappropriate.
Comment 3 Jay Arthanareeswaran CLA 2014-12-11 23:25:16 EST
Shankha, is this same as bug 425420? I doubt, though, as this seems to be happening on the more recent build. Please take a look.
Comment 4 Stephan Herrmann CLA 2014-12-16 10:59:00 EST
S.t. to watch out for: 

(In reply to Error Reports from comment #0)
> we received a new error report for Eclipse 4.4.0.I20140606-1215.

That would be 4.4.0

> General Information:
>     eclipse-build-id:     4.4.0.I20140606-1215

Again 4.4.0

> The following plug-ins were present on the execution stack (*):
>     1. org.eclipse.jdt_3.10.0.v20140925-0400

That would be 4.4.1

>     java.lang.NullPointerException: null
>     at java.lang.String.<init>(null:-1)
>     at
> org.eclipse.jdt.internal.compiler.problem.ProblemReporter.
> conditionalArgumentsIncompatibleTypes(ProblemReporter.java:1572)

In neither 4.4.0 nor 4.4.1 could I match this file&line to any code location that could possibly trigger NPE.

> Messages, stacktraces, and nested status objects may be shortened. Please
> visit 
> http://dev.eclipse.org/recommenders/committers/confess/0.5/reports/-
> for the complete error log.

This link is broken for me.