New for Update 9:
when running inspxe with mi3 on my buggy mpi application (programmed in fortran, using MPICH 3.0.4 and ifort 12.0.5) it detects only an Unititialized memory access in my code in the line of
in module libc.so.6 and in source code line memcpy.S:194.
ierr was initialized before the call. Except of this initialization I do not have any other statement before MPI_INIT (only declarations). My application seems to have some memory currptions later in the program (but is at least executed on all nodes), where inspxe finds nothing.
I am having bluescreen after few seconds of running Inspector. I have tested update 8 and update 9 with the same result.
I have fully-patched Windows 8.1 Pro x64.
from memory dump, windbg.exe says:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
I have fully-patched Windows 8.1 x64, and after I run update 8, or upgrade to update 9, I get bluescreen after running my application for few seconds.
I'm using VS2010. The C++ console app is 32 bit running on Windows 7 x64.
I'm using the Inspector XE update 8.
In our code I am getting 'uninitialized memory access' errors and found this code example on MSDN that mimics the errors in the same locations as our code.
While test-driving Intel Inspector we found out that it will fail to detect memory leaks when multiple Visual C++ runtime versions are loaded in the process.
Has anyone seen this before? Does anyone know if there's a way to point the tool to the specific runtime heap management one wants to inspect.
In our case the exe module is written by us, is compiled with Visual C++ 2008sp1 (MSVCR90.DLL) and brings in a plain C DLL that is built with v2010 (MSVCR100.dll).
Thanks in advance!
I am currently evaluating Inspector XE 2013 for use in an upcoming project. I am experiencing difficulties when attempting to run the sample code ‘tachyon_insp_xe’. Using Visual Studio 2013 I follow the instructions within the tutorial documentation for analysing threading errors, but every time the test I get the following error.
Find_and_fix_threading_errors.exe – Application Error
The application was unable to start correctly (0xc0000005). Click OK to close the application.
I get the following error when trying to run my app. Any pointers on how to fix this? Running from command line using -collect mi1 works but using -collect mi2 or -collect mi3 causes an identical error. Interestingly this happens rather quickly when running the app. This is on windows with the latest Inspector. Interestingly Vtune gives me an identical error running this app.
I could change problem states from New to Deferred(or others) with the Inspector GUI. Is it possible to do that programmatically with a client library? That would allow, for example, multiple developers to update issue states issue management with web interface.
The report files from -report action includes source file and line-number of the offending statement. The corresponding call trace is viewable from Intel-Inspector GUI. Not every developer has a copy of the Inspector on their workstation. Is it possible to produce report including call-stack with inspxe-cl or other command-line tools?
- Page 1