NPE in CreateSymbols caused by bad diagnostic

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • 8
    • Affects Version/s: 8
    • Component/s: tools
    • None
    • b112
    • generic
    • generic

      Crash from CreateSymbols:

      An annotation processor threw an uncaught exception.
      Consult the following stack trace for details.
      java.lang.NullPointerException
         at com.sun.tools.javac.processing.JavacMessager.printMessage(JavacMessager.java:113)
         at com.sun.tools.javac.processing.JavacMessager.printMessage(JavacMessager.java:59)
         at com.sun.tools.javac.sym.CreateSymbols.process(CreateSymbols.java:111)
         at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:757)
         at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$200(JavacProcessingEnvironment.java:97)
         at com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.runContributingProcs(JavacProcessingEnvironment.java:608)
         at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:991)
         at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1149)
         at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1121)
         at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:839)


      Should handle two possible cases of getLocalizedString() which could be null.
      In both cases, the code should roll over to e.getMesage() or even e.toString()

            Assignee:
            Alexander Zuev
            Reporter:
            Jonathan Gibbons
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: