[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-compiler-dev
Subject:    Bug in annotation processing?
From:       Peter Major <peter.major () forgerock ! com>
Date:       2017-10-22 1:27:18
Message-ID: c10f973e-ab96-267a-6154-1704cd4ab571 () forgerock ! com
[Download RAW message or body]

Hi,


I'm running into a strange problem with javac, whereby the internal
state of the Modules object gets messed up and compilation blows up with
an assertion error:

AssertionError
=A0=A0=A0 at jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.ja=
va:155)
=A0=A0=A0 at jdk.compiler/com.sun.tools.javac.util.Assert.check(Assert.ja=
va:46)
=A0=A0=A0 at jdk.compiler/com.sun.tools.javac.comp.Modules.enter(Modules.=
java:250)

I've been trying to track this one down, and so far the only thing I can
see is that the Modules state is initialized correctly, then there is a
newRound call clearing out everything, then Modules inits everything
again, then there is a newRound call from:

=A0 [3]
com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.finalComp=
iler
(JavacProcessingEnvironment.java:1,099)

and the next thing I know is Modules#enter blows up because rootModules
is null. (The correct state would be [unnamed module].)

Is this sufficient amount of information for a bug report, or does this
issue ring a bell for anyone?

Apologies if this is not the right forum.


Best Regards,

Peter Major

[prev in list] [next in list] [prev in thread] [next in thread]