Re: [Bug default/30329] abidiff assertion error in dwarf reader

[Dodji Seketeli <dodji@seketeli.org>]

ben at demerara dot io via Libabigail <libabigail@sourceware.org> a
écrit:

> Frustratingly I've nuked my local build environment for this, but I should be
> able to kick off another build this evening. It should also be reasonably
> straightforward to extent the CI to include this additional debuginfo within
> the tarball.

No problem, thank you for following up.

> Is there an easy way to programmatically extract the path to the alternate
> debuginfo file? I've tested with `objdump -Wk <binary.debug>` which gets me
> something I can run a regex match against, but I'm wondering if there's
> something more direct.

So, here is maybe a starting point.

the ".gnu_debugaltlink" section of the main debuginfo file contains the
path to the alternate debuginfo file.

Let's examine the section headers of the of the main debuginfo file and
see if the .gnu_debugaltlink section is in there:

    $ readelf -S libsqlite3.so.0.8.6.debug | grep .gnu_debugaltlink
      [35] .gnu_debugaltlink PROGBITS         0000000000000000  00201f1c

Right it's in there.

Now, let's read its content, as a string:

    $ readelf --string-dump=.gnu_debugaltlink  libsqlite3.so.0.8.6.debug 

    String dump of section '.gnu_debugaltlink':
      [     0]  /usr/lib/debug/dwz/components/sqlite.bst/x86_64-unknown-linux-gnu
      [    42]  ;?^UW+%^[w^\E^AC^K^:
    $ 

I hope the above is useful.

Thanks again!

-- 
		Dodji