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.
If I profile a method and this method calls another with invoke (over Reflection), then I do not see this in the profiler call graph. Using profiler M2, JDK 1.4.2_05.
It looks like the problem is not due to methods called via reflection, but rather due to some native calls that in turn call Java methods again. Our call graph revelation algorithm cannot determine (so far at least) what methods can be called by a native methods (because native code is much harder to parse/analyze than Java bytecodes), so it misses such calls, or registers only them only for those methods that have been instrumented for other reason. Total instrumentation scheme solves this problem. I asked the user to confirm/comment on the above theory, but have not received a reply yet.
Fixed, code will become available in Milestone 3 release due in the beginning of November. The issue turned out to be related with reflection indeed. Thanks for finally providing a nice test case Thomas!
Verification of old issues.
Closing old issues.
Reverting to the original Target Milestone value changed by mistake. Sorry for inconvenience.