__libdwfl_addrsym is only used in the dwfl_module_addrsym.c source.
There is no need to mark this as a (shared) internal function.
Signed-off-by: Mark Wielaard
---
libdwfl/ChangeLog | 5 +
libdwfl/dwfl_module_addrsym.c | 9 ++---
libdwfl/libdwflP.h| 9 -
3
Since we are single threaded we can just use a static result buffer for
format_dwarf_addr as long as we make sure to print the result before
calling format_dwarf_addr again. This removes lots of malloc/free calls.
On my machine eu-readelf -N --debug-dump=info libxul.so
goes from 57 seconds to 55 s
On my machine eu-readelf -N --debug-dump=info libxul.so > /dev/null
goes from 63 seconds to 57 seconds.
Signed-off-by: Mark Wielaard
---
src/ChangeLog | 7 +++
src/readelf.c | 12 ++--
2 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/src/ChangeLog b/src/ChangeLog
inde
We only call printf on stdout from one thread, so we don't need internal
stdio locking for stdout.
On my machine eu-readelf -N --debug-dump=info libxul.so > /dev/null
goes from 65 seconds to 63 seconds.
Signed-off-by: Mark Wielaard
---
src/ChangeLog | 4
src/readelf.c | 5 +
2 files ch
Hi,
We had a case where dwarf_next_cfi returns -1 but the offset does not update,
as we should expect by the comment:
330 On errors, returns -1. Some format errors will permit safely
331 skipping to the next CFI entry though the current one is unusable.
332 In that case, *NEXT_OFF wi
Hi,
I rearranged the coverage data files a little and turned Lukas' README
into a real script that does the coverage update. See the attached
update-coverage.sh. When there is a new release tagged in git, just
execute it inside the elfutils-htdocs checkout with ./update-coverage
. Wait for the bui
