Wireshark · Wireshark-dev: Re: [Wireshark-dev] Wireshark ABI stability 1.6.4 -> 1.6.5

[Guy Harris <guy@xxxxxxxxxxxx>]

On Jan 13, 2012, at 7:59 AM, Harper wrote:

> Balint Reczey <balint.reczey@xxxxxxxxxxxx>
> wrote in news:4F0ED7C6.2030604@xxxxxxxxxxxx: 
> 
>> I have updated the ABI compatibility report here:
>> http://rbalint.cs.bme.hu/ws-ABI-1.6.4-1.6.5/
> Interesting report. 
> The version numbers in the report are 1.1.0 and 1.1.1, what looks a bit 
> strange.

Perhaps those are library version numbers rather than Wireshark version numbers.  (As stated in another thread, shared library version numbers should *NOT* necessarily be tied to product version numbers.)

> What tool did you used

The ABI Compatibility Checker from the Institute for System Programming of the Russian Academy of Sciences:

	http://forge.ispras.ru/projects/abi-compliance-checker

> and can it also be used to check DLLs?

If by "can it also be used to check DLLs?" you mean "does it work on Windows?", I infer from its INSTALL file:

	http://forge.ispras.ru/projects/abi-compliance-checker/repository/entry/trunk/INSTALL.txt

that the current version works on Windows.  They also list "Linux and FreeBSD" as supported platforms, which probably means "ELF-based systems using the GNU toolchain", so it probably includes the other *BSDs, and might also work on other ELF-based systems if you install the GNU toolchains, in addition to listing Mac OS X.

> Does it investigate the source files or are the binaries touch too?

From the INSTALL file, I infer that it looks at the binaries (the INSTALL file says it uses tools such as readelf, objdump, otool, and dumpbin, which read binaries).