- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
we've written a native 32-bit dll in Win32 that is being interfaced to/called from a 3rd-party application (IDL). We've downloaded an eval version of VTune and would like to profile the Dll, but I'm not sure how to go about profiling it. All my previous experience was using VTune to profile a self-contained executable, not a dll. Can someone point me in the right direction i.e. how to set-up an activity in this case? Thank you in advance.
-L
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There are two data collectors in VTune Performance Analyzer.
1. Sampling data collector, is system wide profiling - all active applications, system modules, device drivers will be monitored.
2. Call graph data collector, is for user's application only - the user can spectify target application (e.g. 3rd-party application)then modify the activity: a) add user's native DLLs(which shouldhas debug info andbase address is relocatable)b) change instrumentation level of 3rd-party application to "minimal"
Regards, Peter
1. Sampling data collector, is system wide profiling - all active applications, system modules, device drivers will be monitored.
2. Call graph data collector, is for user's application only - the user can spectify target application (e.g. 3rd-party application)then modify the activity: a) add user's native DLLs(which shouldhas debug info andbase address is relocatable)b) change instrumentation level of 3rd-party application to "minimal"
Regards, Peter
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