What do I do about the message “(E) ADI checksum (0x84b1c4d) does not match module checksum (0xa1c5e35)." when I register on a .dply file at a remote site?
This message will be followed by specific information about the ADI file and module. The module is the executable or DLL on the remote machine, and the ADI file contains the debug information from the host machine where the workspace was developed. The error messages indicate that the version of the module (application) on the remote machine does not match the version against which you developed your original traces. You must create the workspace and traces against the same version you send tot he remote site because we compare checksums. The only difference is that on Windows, the PDB need not be present on the remote machine because the ADI file contains the information that is needed. Unfortunately on Windows the Visual C++ release build defaults to stripping symbols (on Unix the default is to leave them in). Therefore you need to build to get symbols – you don’t need debug, just symbols. If you do want debug in order to support the full range of probes, then you should build add /Z
Related Questions
- What do I do about the message "(E) ADI checksum (0x84b1c4d) does not match module checksum (0xa1c5e35)." when I register on a .dply file at a remote site?
- I get a warning message about not being able to register memory and possibly out of privileged memory while running on Solaris, what can I do?
- I got an error message when trying to register asking me to email support@spamjab.com?
