This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Documentation about contributing to and running the testsuite
- From: Andrey Ponomarenko <aponomarenko at rosalab dot ru>
- To: Andreas Jaeger <aj at suse dot com>
- Cc: libc-alpha at sourceware dot org, Carlos O'Donell <carlos_odonell at mentor dot com>,Florian Weimer <fweimer at redhat dot com>
- Date: Tue, 07 Aug 2012 19:57:22 +0400
- Subject: Re: Documentation about contributing to and running the testsuite
- References: <5008285D.9030506@redhat.com> <50082BA4.9040609@mentor.com> <20120727181153.239f8b81@spoyarek> <50128F10.2000300@mentor.com> <20120727192620.4a5ad2ab@spoyarek> <5012A75A.7080506@rosalab.ru> <5012ED6C.3010202@suse.com>
Hello,
Andreas Jaeger wrote:
On 07/27/2012 04:36 PM, Andrey Ponomarenko wrote:
Hello,
How about to add a note to this document about existing automated tools
that can be used to check for ABI compatibility issues:
* abi-compliance-checker:
https://github.com/lvc/abi-compliance-checker
I don't know about this tool and I'm curious:
What does abi-compliance-checker bring us that "make check-abi" does
not handle?
According to the documentation [1], "make check-abi" checks "symbol
names and versions and static variable sizes". In addition to this, the
ABI compliance checker tool checks for changes in the layout and size of
data structures, changes in enumerations and constants (#defines),
changes in function parameters and return values, etc [2]. It also
checks source-compatibility of the API.
The tool uses a concept of "ABI dump", that is similar to *.abilist, but
includes much more ABI information. The ABI dump can be created for the
reference glibc version, say 2.10, and compared with the ABI dumps
created for newer versions of glibc.
Can I add a subsection to the "ABI check" section of this document [1]
where I will explain how to run the tool on glibc?
[1] http://sourceware.org/glibc/wiki/Testing/Testsuite#ABI_check
[2]
http://ispras.linuxbase.org/index.php/ABI_compliance_checker#Detectable_Compatibility_Problems
Thank you.
Andreas
--
Andrey Ponomarenko, ROSA Lab.