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.
I've tried a simple test (javac) in standard CPU, Entire app profiling, and "Exclude core classes" checked. I used Direct attachment. When core classes are not excluded, everything is instrumented and results are available. When core classes are excluded, nothing at all gets instrumented. For Java2Demo, on the other hand, core classes excluding works as expected. So, is there any chance this has something to do with the fact that in this javac test class names start with com.sun.*? FYI, our core class filter should only filter out "java.*, javax.*, sun.*, sunw.*" - not sure about the last one, but, anyway, com.sun.* is not considered a JDK core class.
Maybe the question is if current instr. filter behavior is the best one. If you profile Java2Demo with java core classes excluded, the root method (from package java2d) is instrumented because it doesn't match the exclusive filter. If you profile some other application which root method (package) begins by something like "java. javax. sun. sunw. com.sun. org.omg.CORBA org.omg.CosNaming. COM.rsa.", the data cannot be collected because the root method matches exclusive filter and is not instrumented. Solution of this particular problem (javac) is to remove "com.sun." pattern from Java Core Classes filter definition, which definitely shouldn't be there. The problem with root methods not instrumented because of instrumentation filter definition is discussed in Issue# 55454 (http://www.netbeans.org/issues/show_bug.cgi?id=55454), so I'm closing this issue for now.
old issue, closed