- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
is it possible to inspect mixed-mode Visual Studio 2010 unit tests? I.e. the unit test project generates a managed assembly which calls native DLLs; I want to check those native DLLs with Inspector 2011.
When starting the unit test project in VS2010 with context menu "Intel Parallel Inspector 2011 | Inspect Memory Errors", I get the following error message:
is it possible to inspect mixed-mode Visual Studio 2010 unit tests? I.e. the unit test project generates a managed assembly which calls native DLLs; I want to check those native DLLs with Inspector 2011.
When starting the unit test project in VS2010 with context menu "Intel Parallel Inspector 2011 | Inspect Memory Errors", I get the following error message:
Cannot start analysis.
File "mydir\\myfile.dll" is not executable binary.
Regards
- Frank
- Tags:
- CC++
- Debugging
- Development Tools
- Fortran
- Intel® Inspector
- Optimization
- Parallel Computing
- Vectorization
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Frank,
Inspector XE allows to setStartup project for C# language (managed code) and/or C/C++ language (native code). If your Startup project is C/C++ EXE project or C# project which will call native DLLs, it should work.
However if you use ASP.NET to create a unit test to generate a managed assembly (even itcalls native DLLs), but Inspector XE doesn't recognize your ASP.NET project dll, say it is not executable binary. Inspector XE still doesn't support ASP.NET project. This mean, you have to use other EXE (as a caller) to test your native DLLs.
Regards, Peter
Inspector XE allows to setStartup project for C# language (managed code) and/or C/C++ language (native code). If your Startup project is C/C++ EXE project or C# project which will call native DLLs, it should work.
However if you use ASP.NET to create a unit test to generate a managed assembly (even itcalls native DLLs), but Inspector XE doesn't recognize your ASP.NET project dll, say it is not executable binary. Inspector XE still doesn't support ASP.NET project. This mean, you have to use other EXE (as a caller) to test your native DLLs.
Regards, Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Peter,
I am not using ASP.NET; I am using a plain .NET unit test project (i.e. a DLL, not an EXE) calling native C++ DLLs.
The unit test project already is set as Visual Studio's startup project.
Regards
- Frank
I am not using ASP.NET; I am using a plain .NET unit test project (i.e. a DLL, not an EXE) calling native C++ DLLs.
The unit test project already is set as Visual Studio's startup project.
Regards
- Frank
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your target application for Inspector XE should be an EXE.
Native C++ DLLs will be analyzed when your app calls to them.
Native C++ DLLs will be analyzed when your app calls to them.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page