- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I'm trying to find memory leaks with Intel Inspector XE 2016, inside Visual Studio. I'm selecting "Select analysis start location with debugger", it says "Cannot initiate a Microsoft Visual Studio Debugger session". Then it starts my exe, but after hours, nothing has happened. No sign of output anywhere. How can I know what's going on?
- Tags:
- CC++
- Debugging
- Development Tools
- Fortran
- Intel® Inspector
- Optimization
- Parallel Computing
- Vectorization
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What version of Visual Studio are you using? Can you provide a reproducer code?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm experiencing the same problem with Intel Inspector XE 2016 Update 3 Build 460803: when selecting "Select analysis start location with debugger" or "Enable debugger when problem detected" an error is reported: "Cannot initiate a Microsoft Visual Studio Debugger session".
I'm trying this with Visual Studio 2013 (Update 4) and Visual Studio 2015 (Update 2).
About the code/project to reproduce the problem, you can just create a new console application project with Visual Studio 2015 and start Inspector with "Enable debugger when problem detected" or "Select analysis start location with debugger" and you will replicate it systematically. Indeed I've never seen this option working on any project with Visual Studio 2013/2015.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Our engineering team has confirmed this issue and they are investigating it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Our engineering team has confirmed that this is related to a known issue. I do not currently have a timeline for a fix to be implemented.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This should be resolved in our Inspector 2017 version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have same problem with Inspector 2018.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page