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)