Discussion Locked

How to intelligently compare DLL files?

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We use a high level tool called COOL:Gen. This generates C/C++ files and make files. These C/C++ files get built and deployed. Well, in the testing phase people can?t easily see if changes occurred since multiple object are packed into various .dll files. The .dll file size doesn?t say much, since the size is always rounded to the next full blocksize. The date has proven to be unreliable too. All .dlls are regenerated. On top of that, the MS C/C++ compiler does not guarantee that the individual segments inside a .dll are in the same sequence in subsequent compiles.

Therefore, we need a tool or procedure wich analyses the section headers, and then compares the associated code 1 by 1, and reports on differences.

Here is what we do now, but that doesn?t cope with the seqencing problem:

dumpbin /RAWDATA %1.dll >%1.txt
dumpbin /headers %1.dll >%1.hdr
dumpbin /RAWDATA %2.dll >%2.txt
dumpbin /headers %2.dll >%2.hdr
diff %1.txt %2.txt
diff %1.hdr %2.hdr

(question moved from pc-troubleshooting)

3 replies

by ananthap

To analyse the section headers, you can use "View dependencies" that gets installed with visual studio. (Then right click the file name in explorer).

It may be what you need.

Line by line, it won't do. But in your situation, why would you need to take it apart? (I believe you are using a COOL tool precisely to avoid the step of coding).

end

by atjjensen

well, it seems to me that you simply need to check your tools documentation and start enbedding version information into the DLL binary itself. I know the file format supports it, and find it hard to believe the tool would not. Going this route will put the responsibility of updaing version specific information with your Build engineer, wher IMO it belongs and not with the testers. They, should only be insuring that your defined build process is being followed.

Andrew

This discussion is closed to new replies.