- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you recommend any tools for checking memory for corruptions, e.g. uninitialized variables, buffer overruns, etc? I am familiar with the static verifier but its usefulness seems to be limited by the large number of false positives returned.
Thanks.
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well the compiler itself comes withrun-time diagnostics that help identify uninitialised variables and array and string bounds errors.
I have heard ofa memory toolcalled HeapWalker, but I have never used it.
Les
I have heard ofa memory toolcalled HeapWalker, but I have never used it.
Les
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think Les is referring to the /check compile time switch in the compiler. It will add runtime checks for the things you mention.
------
Wendy
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page