[Bug tools/23787] eu-size: Bad handling of ar files inside are files

https://sourceware.org/bugzilla/show_bug.cgi?id=23787 Jack Die changed: What|Removed |Added CC||jackdie3438 at gmail dot com --- Comment #

Re: Will eu-addr2line support debuginfod?

Hi, Vitaly - > Is it planned to have eu-addr2line supporting debuginfod? I try to > pass '[build-id]@address' (in the same format that eu-stack outputting) > without success [...] For a broader discussion of the same topic, see: https://sourceware.org/bugzilla/show_bug.cgi?id=25793 I remain

Will eu-addr2line support debuginfod?

Hi, Is it planned to have eu-addr2line supporting debuginfod? I try to pass '[build-id]@address' (in the same format that eu-stack outputting) without success: # eu-stack -b -p 1 PID 1 - process TID 1: #0 0x7ffa8d4c2886 epoll_wait [c017df57d6194b6479cef409cba575bbaa537c94]@0x7f

[PATCH 3/3] link_map: Inline consider_phdr() into only caller

From: Timm Bäder This gets rid of the tested function and is shorter. --- libdwfl/link_map.c | 66 ++ 1 file changed, 26 insertions(+), 40 deletions(-) diff --git a/libdwfl/link_map.c b/libdwfl/link_map.c index 64baaec4..8a19f358 100644 --- a/libdwfl/

[PATCH 2/3] link_map: Pull read_addrs() in file scope

From: Timm Bäder Get rid of another nested function this way --- libdwfl/link_map.c | 114 ++--- 1 file changed, 66 insertions(+), 48 deletions(-) diff --git a/libdwfl/link_map.c b/libdwfl/link_map.c index 5c39c631..64baaec4 100644 --- a/libdwfl/link_map.

[PATCH 1/3] link_map: Pull release_buffer() into file scope

From: Timm Bäder Get rid of another nested function --- libdwfl/link_map.c | 47 +++--- 1 file changed, 32 insertions(+), 15 deletions(-) diff --git a/libdwfl/link_map.c b/libdwfl/link_map.c index 29307c74..5c39c631 100644 --- a/libdwfl/link_map.c +++ b/l

link_map: Remove nested functions

Hi, the attached patches get rid of nested functions in libdwfl/link_map.c. I wrote these a while back and just looked at them again and we could use the same read_state struct here as well. I just quickly checked, but it seems a bit more involved due to the integrated_memory_callback handling. I