Related articles |
---|
Diff Tools eric.cameron@itt.com (2001-03-26) |
Re: Diff Tools rsnorman@mediaone.net (Richard Norman) (2001-03-27) |
Re: Diff Tools evilzr@yahoo.com (Daniel Dunbar) (2001-03-27) |
Re: Diff Tools broeker@physik.rwth-aachen.de (Hans-Bernhard Broeker) (2001-03-27) |
Re: Diff Tools dennis51@jps.net (Dennis Yelle) (2001-03-27) |
From: | "Richard Norman" <rsnorman@mediaone.net> |
Newsgroups: | comp.compilers |
Date: | 27 Mar 2001 23:22:08 -0500 |
Organization: | Compilers Central |
References: | 01-03-121 |
Keywords: | tools, linker |
Posted-Date: | 27 Mar 2001 23:22:08 EST |
<eric.cameron@itt.com> wrote
> 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.
Same sized executables differing in a few bytes are a time code. You
can see the difference using the DOS command line fc utility (file
compare).
Different size executables are a different problem. These are likely
to involve different compilation or linkage switches, different
library versions, or, to be quite frank, differences in source code.
You can't be sure that these really represent the same code and your
company is correct to be concerned.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.