print_form_data returns the new readp (or readendp on error) to show how
much data was consumed. But when reading the .debug_str_offsets section
we would reuse readp and readendp. This meant the wrong readp would be
returned to the caller.
Signed-off-by: Mark Wielaard
---
src/ChangeLog | 5
It has been only 10 days since the previous release and there are
no functional changes compared to 0.171. The speedup of eu-readelf -N
is pretty nice. And ~25 patches fix various bugs (hangs and crashes)
in dealing with bad DWARF5 data. Most have been found by running the
afl fuzzer on eu-readelf
On Sun, 2018-06-10 at 17:01 +0200, Mark Wielaard wrote:
> Bad DWARF could create a very long or circular DIE ref chain by linking
> DW_AT_abstract_origin or DW_AT_specification to the DIE itself. Break
> the chain after seeing a large number (16) of DIEs.
Pushed to master.
On Mon, 2018-06-11 at 02:18 +0200, Mark Wielaard wrote:
> The afl fuzzer found that we did a wrong check in print_form_data when
> comparing the remaining bytes in the buffer to an (unsigned) value read.
> We were casting the value to ptrdiff_t which is a signed value and so
> might turn a really b
On Mon, Jun 11, 2018 at 11:33:14AM +0200, Mark Wielaard wrote:
> print_form_data returns the new readp (or readendp on error) to show how
> much data was consumed. But when reading the .debug_str_offsets section
> we would reuse readp and readendp. This meant the wrong readp would be
> returned to
ELFUTILS 0.172 - http://elfutils.org/
A new release of elfutils is available at:
ftp://sourceware.org/pub/elfutils/0.172/
or https://sourceware.org/elfutils/ftp/0.172/
* NEWS *
No functional changes compared to 0.171.
Various bug fixes in libdw and eu-readelf dealing with bad DWARF5 data.
Thank
