Can you provide more information regarding how you're exercising the functions in your dll? Do you have an executable which is calling your dll, or are you invoking them directly from a batch? Any additional information you can provide will help determine the best course of action.
Intel Inspector XE is typically
used for memory error and thread checker analysis with C, C++, C# .NET, and
Fortran applications on Windows*- and Linux*-based platforms. It may be possible for Intel Inspector XE to
target, for example, a shell or Perl script which calls an executable binary. You may need to specify the -executable-of-interest
collection action modifier. As a simple example:
Command line example:
inspxe-cl -collect mi2 -executable-of-interest=notepad.exe -- perl test.pl
Where the test.pl simply contains:
I believe the situations noted in earlier posts on this thread relating to dlls would need to be attempted / explored to determine the outcome. How is the dll being exercised? Have you attempted an analysis from the command line with the proposed target? If so, what was the outcome? If not, can you attempt an analysis or provide a simple example of your implementation using a common DLL so others can work with and replicate?
In caseofa general inspection these twosoftware products arevery helpful:
- Depends.exe utility from MS Platform SDK - allows to see all dependent DLLs;
- MS Visual Studio - allows to see and edit resources.
In case of a memory usage analysis:
- Pview.exe and Pstat.exe utilities from MS Platform SDK and, of course, any debugger.