i'm running Visual Studio 2005, Intel VTune 9.0, and Matlab R2006a on Windows XP x64. in matlab, users can write .dll's in C++ and have them loaded into the matlab workspace. the file extension for these dll's is .mexw64 in a 64 bit environment and .dll in a 32 bit environment. when i attempt to profile an application using VTune in my environment, i get:
"Error in module ... ame.mexw64" - File is not valid module
"Error in module ... ame.mexw64" - Module was created for unknown platfor
does it really matter that the .dll is named .mexw64?
Neither x86 nor x64 mex's are genuine dll's even if they masquerade as such. Use the COM builder to create an AX dll that runs outside the Matlab namespace even though it does have a dependency on the redistributable Matlab runtime. Seeif you can profile the COMin vtune. I'm not sure whether or not it can.