| Summary: | Consider changing defaults for using JNI vs forking on different platforms | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Andrew Niefer <aniefer> |
| Component: | Launcher | Assignee: | Project Inbox <equinox.launcher-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jamesblackburn+eclipse, krzysztof.daniel, overholt |
| Version: | 3.4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
|
Description
Andrew Niefer
Given bug 339788 can this be configurable? I primarily use x86_64 and it has been useful in the past for me to see the Java invocation command (to debug launch parameters, etc.). Presumably jstack, jps, jconsole etc. work for the JNI'd java? On all platforms except the mac, you can specify which one to use by setting the -vm argument. If the -vm arg points to a java executable, then we will fork. If the -vm arg points to a (libjvm.so/jvm.dll) shared library, then we will attempt JNI invocation. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug was marked as stalebug a while ago. Marking as worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag. This bug was marked as stalebug a while ago. Marking as worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag. |