-
Notifications
You must be signed in to change notification settings - Fork 114
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
UnsatisfiedLinkError
in native GraalVM image
#159
Comments
Thanks for reporting! This looks like a very early failure of loading the native shared library, which is very unexpected. Which GraalVM version do you use to build the native-image? Can you provide a description how you build it? What happens when you launch your program with
(copy the dylib to a regular directory in the file system first, and make sure to specify an absolute path) |
We are using GraalVM version 17 to build our application. The build is Gradle based and we have set a lot of different options, but I will try to gather them. I didn't yet try using that override property, but what I did try and found to be working is if I place the dylib file next to the executable, then it all works. |
@knutwannheden This could be due to a GraalVM issue with resource: URLs. Please definitely re-try with the latest GraalVM and report back. Thanks! |
Thanks for the update. I will definitely try that out then. |
Describe the bug
We are building a GraalVM native image and at runtime we are getting the following exception when calling
AFUNIXSocketAddress#of(Path)
. Before adding too many possibly irrelevant details, I include the stack trace with all the listed suppressed exceptions, as I found a few related issues, where this information was requested.FWIW, I used to
strings
tool to make sure that the native libraries are actually contained in the GraalVM native image and I found these.dylib
entries:To Reproduce
As GraalVM builds generally appear to be supported, it looks like this issue must be something specific to our build setup. But possibly the information provided is already enough to track this down.
Expected behavior
Successful loading from GraalVM native image.
Output/Screenshots
See above.
When running the application in non-native mode everything works as expected.
The text was updated successfully, but these errors were encountered: