Hi Neil, The stack trace doesn't suggest a not attached thread by itself.
The stack trace simply allows us to follow the calls being invoked, and a look at the source code is what suggests that env->AttachCurrentThread (or AttachCurrentThreadAsDaemon) is not being invoked. Attaching native threads to the proper JVM threads is mandatory (so the JVM's JNI can work properly).
Hopefully we'll have Matthias' fix in place soon! :-) Cheers, Antonio El 9/4/21 a las 13:41, Neil C Smith escribió:
It's been a long while since I've looked at this (in context of JNA callbacks), but I'm curious why that stack trace would suggest specifically a not attached thread? Would it not fail earlier?
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
