[Bug tools/21332] elflint doesn't handle compressed sections

2017-04-05 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=21332 --- Comment #7 from Mark Wielaard --- Turns out supporting (gabi) compressed ELF sections in eu-elflint is is fairly simple by just decompressing every section unconditionally at the start (when we also check if all sections are actually there

[PATCH] elflint: Support checking ELF files with compressed sections.

2017-04-05 Thread Mark Wielaard
Simply unconditionally uncompress any section to make sure indexes between sections check out. Add some testcases with various compressed sections. https://sourceware.org/bugzilla/show_bug.cgi?id=21332 Signed-off-by: Mark Wielaard --- src/ChangeLog | 4 src/elflint.c

[Bug libdw/21330] dwarf_peel_type() loops infinitely for typedef const struct ...

2017-04-05 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=21330 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

Re: dwfl_attach_state alternative taking Ebl?

2017-04-05 Thread Milian Wolff
On Wednesday, April 5, 2017 2:46:34 PM CEST Mark Wielaard wrote: > On Thu, 2017-03-30 at 13:14 +0200, Milian Wolff wrote: > > > OK. How do you know the Elf architecture in that case? How and by what > > > is it given? Is that an EM constant or some architecture string? > > > > In our case we eithe

Re: dwfl_attach_state alternative taking Ebl?

2017-04-05 Thread Ulf Hermann
> So you map from simple architecture name like "x86" or "powerpc". But > what mechanism do you have to whether that is 32 or 64 bit, and big or > little endian? The code can be extended to provide that information. We know it in advance, but didn't need it so far. Ulf

Re: dwfl_attach_state alternative taking Ebl?

2017-04-05 Thread Mark Wielaard
On Thu, 2017-03-30 at 13:14 +0200, Milian Wolff wrote: > > OK. How do you know the Elf architecture in that case? How and by what > > is it given? Is that an EM constant or some architecture string? > > In our case we either get it from perf, or the user specifies it directly on > the command lin