- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Evaluating Intel Inspector 2017
I'm trying to locate deadlocks and race conditions in our game project, but analysis is running way too slow. I've include only one dll module (using Include only following modules option in project properties), stack frame depth 1, no suppression, project is compiled on release, /Zi, with optimalizations. It takes minutes just to load dll(s) and show splash screen and it would probably take hours to get to main menu and do actual analysis.
How can i make it run faster? Can i attach to running process and instrument code later on.
Thanks
Andrew
- 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
There are APIs to tell the collector when to start and when to stop - see here: https://software.intel.com/en-us/node/622478 Would that be an option for you?

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