ELFUTILS 0.171 - http://elfutils.org/
A new release of elfutils is available at:
ftp://sourceware.org/pub/elfutils/0.171/
or https://sourceware.org/elfutils/ftp/0.171/
* NEWS *
DWARF5 and split dwarf, including GNU DebugFission, are supported now.
Data can be read from the new DWARF sections .de
On Fri, 2018-06-01 at 13:23 +0200, Mark Wielaard wrote:
> We would give up if one of them failed. With this fixed a self-test with
> make check succeeds when building elfutils itself with CFLAGS set to
> "-gdwarf-4 -gdwarf-split -O2".
Pushed to master.
On Fri, 2018-06-01 at 04:11 +0200, Mark Wielaard wrote:
> Commit 314e9d7d "readelf: Handle .debug_info first if any other debug
> section needs it" disabled section_info printing if it was already
> handled. But section_types was an alias for section_info. So unless
> section_info was explicitly pr
On Fri, 2018-06-01 at 02:51 +0200, Mark Wielaard wrote:
> Normal and split dwarf from GNU DebugFission look the same, but should
> be treated competely separtely. When having a file with both skeletons
> and real compile units only note the secoffsets into the real .debug_loc
> in readelf. Otherwis
We would give up if one of them failed. With this fixed a self-test with
make check succeeds when building elfutils itself with CFLAGS set to
"-gdwarf-4 -gdwarf-split -O2".
Signed-off-by: Mark Wielaard
---
libdw/ChangeLog | 7 +++
libdw/libdw_find_split_unit.c | 114 +
On Thu, 2018-05-31 at 14:40 +0200, Mark Wielaard wrote:
> Introduce testrun_on_self_exe and testrun_on_self_lib.
> Some tests cannot handle (unrelocated) ET_REL object files.
> run-get-units-split.sh and run-unit-info.sh only handle executables
> and shared libraries. This allows running the whole
On Thu, 2018-05-31 at 14:16 +0200, Mark Wielaard wrote:
> Test that the low high pc attributes can be properly resolved also
> in split dwarf setups.
Pushed to master.
On Wed, 2018-05-30 at 17:32 +, Sasha Da Rocha Pinheiro wrote:
> I just fixed something interesting in Dyninst. We were assuming that
> the FDEs were following the CIE in the eh_frame section, but this is
> not correct. I found them mixed in an ARM binary and this caused
> wrong parsing.
> So w