|Diff Tools email@example.com (2001-03-26)|
|Re: Diff Tools firstname.lastname@example.org (Richard Norman) (2001-03-27)|
|Re: Diff Tools email@example.com (Daniel Dunbar) (2001-03-27)|
|Re: Diff Tools firstname.lastname@example.org (Hans-Bernhard Broeker) (2001-03-27)|
|Re: Diff Tools email@example.com (Dennis Yelle) (2001-03-27)|
|Date:||26 Mar 2001 13:44:09 -0500|
|Organization:||NewsOne.Net - Free Usenet News via the Web - http://newsone.net/|
|Keywords:||tools, linker, question|
|Posted-Date:||26 Mar 2001 13:44:09 EST|
I've encountered a documented problem within Visual C++, that the
same code will produce different sized executables, when compiled at
different times or on different machines.
Now, the problem is, my company wants to be able to see the
differences between these two executables. If they are just time/date
stamps, that's fine, but if there is other stuff (memory contents,
etc) there may be problems, and we have to be able to determine that.
We'd like a more programmatic way of doing this then using a hex
editor, but any suggestions are helpful.
Return to the
Search the comp.compilers archives again.