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 55448 - We should not attempt to instrument unlinked classes
Summary: We should not attempt to instrument unlinked classes
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: mishadmitriev
URL:
Keywords:
Depends on:
Blocks: 55306
  Show dependency tree
 
Reported: 2005-02-24 00:24 UTC by mishadmitriev
Modified: 2007-02-20 18:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mishadmitriev 2005-02-24 00:24:50 UTC 
See the last question/explanation on
http://profiler.netbeans.org/faqs.html 
Basically, if during redefinition a profiler
stumbles upon an unlinked (see JVM Spec) class C,
it tries to link it. If C references some other
class D, and D is not on class path, linking
fails, the profiler prints an error and doesn't do
instrumentation. We could do better (in JDK 1.5 at
least) by checking in advance which classes aren't
linked, and not attempting to instrument them
until they are actually linked (which may never
happen).
Comment 1 mishadmitriev 2005-03-10 03:49:50 UTC 
Issue 55306 seems to indicate that in extreme cases, attempting to instrument a
class that is not linked can result in a ClassCircularityError. Thus this issue
needs to be addressed not just out of usability reasons.
Comment 2 mishadmitriev 2005-03-10 04:45:06 UTC 
Fixed in M6.
Comment 3 ehucka 2006-10-09 12:11:42 UTC 
Verification of old issues.
Comment 4 Alexander Kouznetsov 2007-02-12 22:37:03 UTC 
Closing old issues.
Comment 5 Alexander Kouznetsov 2007-02-20 18:29:28 UTC 
Reverting to the original Target Milestone value changed by mistake. Sorry for
inconvenience.