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 have a project which needs to run in 32-bit due to a dependency on 32-bit *.dll's in Windows. The project is configured to use the 32-bit version of jdk 7. The debugger works well and there are no problems when it loads the 32-bit *.dlls. However, if I click on a class with a "public static main(String[]args)" method and choose "Profile File", it looks like the profiler starts and tries to attach, then everything stops. There is no jvm running and the profiler itself thinks the profile session is done. There are no profiler results though. When I look at the log, I see the following: "profile: Error occurred during initialization of VM Could not find agent library C:/netbeans/profiler/lib/deployed/jdk16/windows-amd64/profilerinterface.dll in absolute path, with error: Can't load AMD 64-bit .dll on a IA 32-bit platform Java Result: 1 BUILD SUCCESSFUL (total time: 2 seconds)" So, I think what is happening is the IDE is running as 64-bit, so it assumes the agent library to use should also be 64-bit, but in this case it should be the 32-bit version in "C:\netbeans\profiler\lib\deployed\jdk16\windows\profilerinterface.dll" Is there any way to force it to use the correct profiler dll?
Created attachment 133438 [details] Profiler Dialog Does Not Detect 32-bit The Profiler dialog does not appear to be aware of the 32-bit dll's for some reason.
Created attachment 133439 [details] Can't Attach to 32-bit Debug Session Ran app in the debugger with a breakpoint set. Then tried to attach the debugger, but failed with this error.
Please try NetBeans 7.4 beta. Profiler uses JDK configured for your project and it should correctly detect if the JDK is 32bit or 64bit. The attach wizard is now aware of the 32-bit dll's.