> On Oct 19, 2015, at 11:01 PM, Mandy Chung <[email protected]> wrote: > >> >> On Oct 19, 2015, at 6:04 PM, Alan Bateman <[email protected]> wrote: >> >> On 19/10/2015 22:58, Mandy Chung wrote: >>> Hi Chris, >>> >>> Thanks for reporting this (this is not a known issue). >>> >>> java.lang.InternalError: unnamed package in named module java.base >>> >>> The case with the unnamed package defined by the boot loader is the types >>> from -Xbootclasspath/a. Is -Xbootclasspath/a being used? >> Definitely something not right here as it looks like a type defined to the >> boot loader that is in the unnamed package but it's module field set to >> java.base. It feels like a corruption issue, either that or somehow a type >> in the unnamed package was loaded really early (before java.base is defined) >> and has somehow been patched to in the java.base module. > > I pushed a fix to include the class name in the InternalError. If Chris is > building jake, would you mind pulling down the patch and troubleshoot this > and find out what class in the unnamed package?
Please keep me posted on this as well, sounds like it could be a bootstrapping issue in the JVM where we patch classes that are loaded before java.base is defined. Thanks, Lois > > thanks > Mandy
