Re: [PATCH] elfclassify: Handle fwrite to stdout failing.

2020-07-23 Thread Mark Wielaard
On Sun, 2020-07-19 at 19:41 +0200, Mark Wielaard wrote:
> In theory an fwrite can fail, if so, signal it by calling issue ().

Pushed to master.


[Bug tools/25793] eu-readelf -w dumps incomplete even if debuginfod available

2020-07-23 Thread woodard at redhat dot com via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=25793

Ben Woodard  changed:

   What|Removed |Added

 CC||woodard at redhat dot com

--- Comment #4 from Ben Woodard  ---
I think that keeping the default the same is fine but I think we should add an
option to make it possible like the suggested "--dwarf=follow-links" and change
the error to: "eu-readelf: cannot get debug context descriptor: No DWARF
information found. Try: —dwarf=follow-links"

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Re: [PATCH] Only typedef Ebl once.

2020-07-23 Thread Mark Wielaard
On Sun, 2020-07-19 at 22:03 +0200, Mark Wielaard wrote:
> Since commit 287a18452 libasm.h defines an opague Ebl handle.
> This is fine, except for (internal) code that also includes libebl.h.
> Since C11 having multiple typedefs for the same thing is fine, but we
> do build using GNU/C99. This also allows multiple same typedefs,
> except
> for (very) old GCCs.
> 
> This only affects internal code, since libebl.h isn't a public
> header.
> 
> For internal code, only add the typedef in libebl.h when libasm.h
> hasn't been included. Make sure all code that includes both headers
> includes libasm.h first.

Pushed to master.