As mentioned elsewhere, during netcat I found that attempting to
profile Java applications under Windows crashes the JVM. This is
reported as https://issues.apache.org/jira/browse/NETBEANS-1428 and
thanks to work by Eduardo Quintanilla, it appears that Java 9 and
later are all affected.
I'd like to try and help if possible but I need a bit of advice to get
started. As I understand it, profiling an application starts a new JVM
with an agent specified on the command line. This agent loads native
code to do its work.
Is there a way to attach a debugger to the agent code (rather than the
profiled application code?) I think a Java debugger would be fine as a
first step then I can see what values get passed to the native code.
Thanks,
Pete

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Reply via email to