Access violations under BoundsChecker and Win2k sp4

0 Likes

Problem:

BoundsChecker/Error Detection crashes my applications with an access violation when I run with memory tracking enabled. I recently installed service pack 4 for Windows 2000

Resolution:

If you recently installed service pack 4, the debug symbols on your system may be out of date. Microsoft does not update the symbols when the service pack installs.

One easy way to check is to compare the versions and dates of the modules installed with sp4 and their associated .pdb files. If the .pdb files are older than the .dlls, you need to download the files form Microsoft. Another quick check is to rename some of the .pdb files (for example, rename RPCRT4.pdb to _ RPCRT4.pdb) and see if that eliminates the access violation under BoundsChecker. BoundsChecker trusts the symbols in the .pdbs implicitly, and if the function addresses in the file don't math the actual addresses in the binary, BoundsChecker attempts to patch garbage memory, resulting in the access violation.

<!--- END INSERT ANSWER --->

Old KB# 11583
Comment List
Anonymous
Related Discussions
Recommended