-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Unsupported method java.lang.Class.getConstantPool() is reachable #3125
Comments
@aldettinger Please pass --report-unsupported-elements-at-runtime flag in your build arguments for native-image |
thanks for having a look @mcraj017. Setting
And then setting Are there any tips to find the piece of code that make the static analysis fail in such a situation ? |
I was able to go beyond this issue by substituting RedissonLiveObjectService.createProxy(...) and Introspectior.getFieldsWithAnnotation(...) where byte buddy is used. It would be nice to have a way to find the culprits quicker in such a situation. Maybe there is a way for native-image to exhibits stack traces mentioning |
@aldettinger please share the full error stack |
@mcraj017 The full error stack is present in the first note. |
@aldettinger I am able to build the image using --report-unsupported-elements-at-runtime and solution from quarkusio/quarkus#6123
instead of
|
@mcraj017 thanks for taking a look. The resteasy-jackson issue is not related to the original bytebuddy issue. As such, the original stack trace from the first note can be reproduced even when the The original byte buddy issue is a static analysis issue only, as such using From there, I'm wondering whether the main value for the community would be to have a way to better diagnose such situations. Is it possible to have a better stack trace ? Is there an existing option that can provide more information ? What do you think ? |
@aldettinger Native-Image is an early adopter technology and we are making it better with every new release. --report-unsupported-elements-at-runtime options will be depreciated in future releases when native-image is compatible with all the JVM features. |
Describe the issue
Static code analysis including
RMap<Object,Object> org.redisson.api.RedissonClient.getMap(String name)
reportsUnsupported method java.lang.Class.getConstantPool() is reachable
Steps to reproduce the issue
Describe GraalVM and your environment:
GraalVM Version 20.3.0 (Java Version 11.0.9+10-jvmci-20.3-b06) on RHEL 7.9
Any idea to find the culprit ? Are we searching a call to
System.getProperty(String, String)
? orTypeVariable.getAnnotatedBounds()
?The text was updated successfully, but these errors were encountered: