- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 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
Send me the affected result directory in a private message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Was it possible that this was due to no enough memory to work when Inspector ran?
Did you build 32bit application but running in 64bit system? If so, please use option "/LARGEADDRESSAWARE" to build your 32bit app.
Can you try this in Inspector standalone app (inspxe-gui), or command line (insplxe-cl) ?
Can you set stack-depth=1 to reduce memory consumption from Inspector's monitoring? Or set option "-module-filter-mode=include -module-filter=your-program" for your target module only?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mark may understand pin log better. Have you sent result directory to Mark?
Sending problematical application to Mark, also will be helpful, I think, if possible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still have other thing to try, in command line:
inspxe-cl -collect mi2 -r /tmp/r000mi -module-filter-mode=include -module-filter=your-module -- ./your-app
Will you see same result? Or application exits abnormally?

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