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.

Bug 47556 - VM error when trying to attach
Summary: VM error when trying to attach
Status: CLOSED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: mishadmitriev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-20 14:52 UTC by anovak
Modified: 2007-02-12 22:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
problem desc (1.67 KB, text/plain)
2004-08-20 14:52 UTC, anovak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description anovak 2004-08-20 14:52:11 UTC
Attached invocation fails immediately.
Comment 1 anovak 2004-08-20 14:52:46 UTC
Created attachment 16983 [details]
problem desc
Comment 2 anovak 2004-08-20 14:55:50 UTC
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.
 
 
Comment 3 mishadmitriev 2004-09-08 00:04:14 UTC
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.
Comment 4 ehucka 2006-10-09 12:08:48 UTC
Verification of old issues.
Comment 5 Alexander Kouznetsov 2007-02-12 22:27:23 UTC
Closing old issues.
Comment 6 Alexander Kouznetsov 2007-02-12 22:27:38 UTC
Closing old issues.