-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 on using JNA direct calls with YourKit Java Profiler instrumentation #236
Comments
Supply a FunctionMapper in your library options when you call Native.register(NativeLibrary) which strips the Even with a type mapper, I'm not certain it'd work; I don't recall offhand if the direct mapping even makes use of a supplied FunctionMapper if one exists in the options. On May 28, 2013, at 12:47 PM, traff wrote:
|
I've verified that direct mapping does take into account any supplied |
Thanks a lot for the quick and detailed answer! I'll try to supply FunctionMapper, althought it's not my library that uses JNA. |
Addressed in 3704b23 |
Motivation: Now that we support cross-compiling to aarch64 we should also do so during PR builds and normal builds Modifications: Add workflow config for aarch64 Result: Ensure we can always build for aarch64 as well
Running JNA code with YourKit Java Profiler agent I get the following error
Read response from YourKit guys for details: http://forums.yourkit.com/viewtopic.php?f=3&t=3299#p10809
Also this suggestion can be usefull: https://groups.google.com/forum/?fromgroups#!topic/jna-users/z-n85N0emSw
The text was updated successfully, but these errors were encountered: