Steps to reproduce:
1) Checkout and build the UML cluster from the trunk.
2) Launch NB 6.0, add jkd1.5 via the Java platform manager, calibrate the profiler.
3) Open the uml core project. Do not open any required projects.
4) Right-click on uml core -> Profile
IDE log and profiler output attached.
Created attachment 54432 [details]
Created attachment 54433 [details]
Workaround: install NetBeans in a location without spaces in the pathname.
When NetBeans is installed in a location with space in path, profiling NetBeans modules using Profile Project action
doesn't work ("Could not find agent library in absolute path..."). This seems to have been broken for a long time,
reproduced also with NB 6.1.
Fixed for 6.5.
date: Tue Sep 02 12:50:45 2008 +0200
summary: Bugfix #124345 Fixed profiling nbmodules on Windows, SPACE_IN_PATH
Integrated into 'main-golden', will be available in build *200809031401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jiri Sedlacek <email@example.com>
Log: Bugfix #124345 Fixed profiling nbmodules on Windows, SPACE_IN_PATH
Still reproducible for NetBeans 6.5 rc1.
"Error occurred during initialization of VM
Could not find agent library in absolute path: E:/Program
Product Version: NetBeans IDE 6.5 RC1 (Build 200810151402)
Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b13
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)
Created attachment 71984 [details]
The issue has been reopened by mistake, the described problem is fixed. Profiling source modules of the IDE works fine
when using IDE installed in path containing space. Updating the summary to better describe what's this issue about.