From: Tom Tromey <tromey@redhat.com>
To: Martin Runge <martin.runge@web.de>
Cc: Joel Brobecker <brobecker@adacore.com>,
John Gilmore <gnu@toad.com>,
gdb@sourceware.org,
Martin Runge <martin.runge@rohde-schwarz.com>
Subject: Re: RFC: include mod time and size in DWARF file name table
Date: Tue, 15 Jan 2013 17:51:00 -0000 [thread overview]
Message-ID: <87bocqjpw6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAF4KFGpZVzH0sseUyAkCJiTT+MU0QyNEWPNQ8EL8yhsrQZ=i2w@mail.gmail.com> (Martin Runge's message of "Mon, 14 Jan 2013 13:00:10 +0100")
>>>>> "Martin" == Martin Runge <martin.runge@web.de> writes:
Martin> Imagine an executable that uses a library. The executable is not
Martin> changed very often, but the library is rebuild every day. If the
Martin> library's interface (defined in a header file included by both)
Martin> changes, you get a process (the executable with the library loaded)
Martin> that knows two versions of the things defined in that header file. How
Martin> can this be detected, once the wrong build messed things up?
I would suggest writing a tool to check the ABI using the debuginfo.
Then you can compare types between the executable and the library.
There are already some ABI checkers out there, maybe one would suit your
purposes.
Tom
prev parent reply other threads:[~2013-01-15 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 13:24 Martin Runge
2013-01-13 4:19 ` John Gilmore
2013-01-13 5:54 ` Joel Brobecker
2013-01-14 12:31 ` Martin Runge
2013-01-15 17:51 ` Tom Tromey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bocqjpw6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=gnu@toad.com \
--cc=martin.runge@rohde-schwarz.com \
--cc=martin.runge@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox