- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I asked this on the Vtune forum but didn't get much response.
I follow the instructions on using the "release" build and adding the debug/full but all I get from VTune is a lump -- not broken out by routines (addressses which are way hard to read). The only way I've been able to get it to work is to start with debug build and work backwards for optimizations.
What's the trick? Linking with debug libs? Wasting lots of time trying to get this to work.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You should be able to set /Zi in your release build compile and link steps, if you don't care about full detail from the libraries. The analyzer will need the search paths set including the .pdb .obj and .exe.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, I'll give that a try. Instructions may be lagging behind?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And /Zi seems to help with the release build and debug/full. Thanks!
Oops -- spoke too soon. That was with a debug build. Release build even with /Zi doesn't work in VTune.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That tutorial doesn't mention the need to set the linker debug flag (in VS set Linker > Debugging > Generate debug info to yes).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, Ian. I'll try that then.
Tutorials are of less use if they don't explain all the steps....
And it keeps complaining that I am using the debug configuration for the VTune. :-)

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page