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.
1) cd to the bin directory where Sun Studio's binaries are including compilers and er_print. 2) start NetBeans 3) run any app with SunStudio profiler configuration on dlight profiler doesn't work (no details) and many exceptions are thrown: java.io.IOException: Failed to start er_print at org.netbeans.modules.dlight.perfan.storage.impl.ErprintSession.restartAndLock(ErprintSession.java:180) at org.netbeans.modules.dlight.perfan.storage.impl.ErprintSession.getExperimentStatistics(ErprintSession.java:199) at org.netbeans.modules.dlight.perfan.spi.MonitorsUpdateService$Updater.run(MonitorsUpdateService.java:213) at org.netbeans.modules.dlight.util.DLightExecutorService$2.run(DLightExecutorService.java:89) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:602) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1084)
This scenario is actually not very uncommon. The Sun Studio IDE (based on NB6.8) is in the same directory as compilers and er_print, and when I start he IDE, I very often cd to Sun Studio's bin directory and start the IDE with this command: ./sunstudio. And then profiling doesn't work because of this bug.
There is a bit more to this bug. er_print is not found when I'm in the bin directory, but it is also not found when I'm in the directory above bin! It works fine if I start sunstudio with 'opt/SUNWspro/bin/sunstudio'.
Thomas, where I can try to reproduce the bug? Where I can get the Sun Studio IDE (based on NB6.8) ?
It has nothing to do with Sun Studio. I could easily reproduce it with plain NetBeans but only if I started Netbeans in the Sun studio bin directory. Sun Studio makes the bug 'worse' because it is more common to start NetBeans (through the SS IDE) in Sun Studio because SS IDE and SS binaries are in same directory. Let me see if I can see the bug in today's NNB build.
Try SS in /set/sstrunk/pibareas/ide/master/091109/inst/intel-S2.inst/opt/SUNWspro/bin 1) cd to the above folder 2) start sunstudio 3) run any (Fractal) app and you will see the exceptions when clicking on the CPU details button. The above build is based on today's NB 6.8. Just an idea: could the IO exceptions be caused by the fact that the directories here are read only?
Something strange is going on. It looks more and more like a race condition somewhere because the bug comes and goes without a clear set of steps to reproduce. I can reproduce it almost every time if I cd to the SS bin directory (which is on a server) and using a new user directory (on a different server).
Changeset: http://hg.netbeans.org/cnd-main/rev/0d23a5567ef3
As it turned out, the real reason is the length of path to the bin directory of er_print. I used too small constrains...