This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | VM error when trying to attach | ||
|---|---|---|---|
| Product: | profiler | Reporter: | anovak <anovak> |
| Component: | Base | Assignee: | mishadmitriev <mishadmitriev> |
| Status: | CLOSED INVALID | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 4.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | problem desc | ||
|
Description
anovak
2004-08-20 14:52:11 UTC
Created attachment 16983 [details]
problem desc
Strange enough, when I avoid to add .../../jfluid.jar in
bootclasspath, another VM crash appears, but now it starts with
(notice boot classpath!):
JVM_OnLoad called...
JFluid: can't start the profiler back end: main class not found
JFluid: boot class path was set to: b/rt.jar
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x400A87F9
Function=(null)+0x400A87F9
Library=/lib/libc.so.6
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
This is not a real issue, since it was caused by using wrong settings (incorrect VM startup parameters). To avoid it in future, the relevant part of the documentation has been made more clear. The fact that the VM crashes in case of this misuse can be viewed as an issue by itself, but I couldn't reproduce it. And since this (attach on startup) seems like a rarely used feature, and such a misuse is probably even more rare, I think it's not worth spending more time trying to reproduce/fix this remaining problem. Verification of old issues. Closing old issues. Closing old issues. |