Re: [PATCH] Add support for the CTF debug format to libabigail.

[Dodji Seketeli <dodji@seketeli.org>]

[...]

"Jose E. Marchesi via Libabigail" <libabigail@sourceware.org> a écrit:

>>> - The libabigail tools assume that ELF means to always use DWARF to
>>>   generate the ABI IR.  We added a new command-line option --ctf to
>>>   the tools in order to make them to use the CTF debug info instead.
>>>   We are definitely not sure whether this is the best user interface.
>>>   In fact I would be suprised if it was ;)
>>>
>>> - We added support for --ctf to both abilint and abidiff.   We are not
>>>   sure whether it would make sense to add support for CTF to the other
>>>   tools.  Feedback welcome.

[...]

Giuliano Procida <gprocida@google.com> a écrit:

>> For ease of testing / building up a useful regression test suite, please do
>> consider adding --ctf to abidw (or adding abictf?) which would give a
>> CTF -> XML utility. Plain diff (rather than abilint's ABI diff) can be used to
>> check for changes over time.

"Jose E. Marchesi" <jose.marchesi@oracle.com> a ecrit

> What about renaming abitdw to something like abielf?  Then --ctf would
> fit well.

abidw was also a word play for "abi data write".  So we can just let it
as it is and add --ctf to it.  But if you feel strongly about it, we can
indeed change the name and provide an 'abidw' symlink for compatibility
purposes.  The new name could be 'abisrl' for 'abi serialize", or
something.

But we can discuss this later when the feature is in place.  For now, I
think the most important thing to do is to add the --ctf option to
abidw.

Ultimately, I think we can write some magic to detect the debuginfo
format associated with the binary and use it.  There will be cases where
it's hard to determine that.  For those cases, the --ctf or --dwarf (to
be added) options would be useful.

I hope this is helpful.

[...]

Cheers,

-- 
		Dodji