New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JDK 17: --illegal-access=permit
removed
#3355
Comments
Below are lines that appended to launch.properties for ghidra 9.2.4 working in windows 10 - eclipse-temurin-java17-beta. VMARGS=--add-opens=java.base/java.util=ALL-UNNAMED |
Did you find that you needed every entry there? |
No, These are borrowed lines required to intelijidea working in 17. and It made ghidra working in 17 too. |
@ryanmkurtz I saw there's a related issue in gson: google/gson#1875. The workaround is to add |
Yep, we'll need to add that one. Thanks for letting me know! |
On Windows 10 with JDK 16.0.1, I'm still getting the following warning: |
We need an --add-opens for that package on Linux so the application title gets set correctly, but unfortunately when you reference that package on Windows you get that new warning. It's not a problem in a build because we support platform-specific JVM arguments in |
Was there a separate issue tracking fixing this for Ghidra Server? For now, I just hacked it in with a giant environment variable with |
See #3406 |
You probably want to unpin the issue now, after it was fixed. |
The main point of pinning it was to try to prevent duplicate tickets from being generated. Now that Java 17 is out, that is more likely than before. Hopefully people will see it pinned and see the fix is to upgrade to 10.0.3. |
There are some known issues with Ghidra and JDK 17, which is scheduled to be released on 09/14/2021.
This issue is to address the
OpenJDK 64-Bit Server VM warning: Ignoring option --illegal-access=permit; support was removed in 17.0
warning you get when launching Ghidra with JDK 17.The following table outlines how each illegal access can occur within Ghidra. The bold entries are relevant to the Ghidra client application:
Solution:
Add the following JVM arguments to
launch.properties
andGhidra.launch
:An equivalent solution will have to be implemented for tests and the server, which do not currently use
launch.properties
. That will be handled in a different ticket.If this is not fixed, several jars that perform illegal reflective accesses will not function properly, as we saw with JDK 16 in #2879, #2888, #2904, #2999, and #3030.
The text was updated successfully, but these errors were encountered: