I'm using Intel Inspector to check for memory issues with my program and I keep running into "uninitialized memory access" errors in the MSVCR90D.dll modules but when I click on tha开发者_StackOverflowt error, it says no source could be displayed. Any ideas what I'm doing wrong to cause this to happen?
I have a suspicion that it has something to do with my read in/output functions but how can I be sure?
MSVCR90D.dll is the debug version of the Microsoft Visual C++ 9.0 Runtime (CRT). At the expense of speed and memory use, the debug CRT contains additional verification (especially around memory management) to help you diagnose memory issues in your program.
It is quite possible that the error checking mechanisms in MSVCR90D.dll are interfering with the issue detection mechanisms in the Intel Inspector. Alternatively, this might be a real issue that is being caught. If you have the call stack at the point of the uninitialized memory access, you might be able to tell what uninitialized object is being accessed.
Additionally, you should try using the Intel Inspector on Release builds instead of Debug builds.
use Dependancy walker for your dll to find the exact corrupt function
精彩评论