[Bug libdw/30980] offline.c:53: dwfl_offline_section_address: Assertion `mod->e_type == ET_REL' failed.
https://sourceware.org/bugzilla/show_bug.cgi?id=30980 Sam James changed: What|Removed |Added CC||sam at gentoo dot org See Also||https://github.com/systemd/ ||systemd/issues/29585 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug tools/31085] New: Provide tool to extract path to .dwo from binary
https://sourceware.org/bugzilla/show_bug.cgi?id=31085
Bug ID: 31085
Summary: Provide tool to extract path to .dwo from binary
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tools
Assignee: unassigned at sourceware dot org
Reporter: sam at gentoo dot org
CC: arsen at sourceware dot org, elfutils-devel at sourceware
dot org
Target Milestone: ---
It would be nice if elfutils provided a tool to find the .dwo path embedded in
a binary with gcc's -gsplit-dwarf (extract '.debug_str' to find the .dwo path).
```
echo 'int main() {}' > /tmp/foo.c
gcc /tmp/foo.c -ggdb3 -o /tmp/foo -gsplit-dwarf
```
/tmp/foo might be moved after the build (e.g. installed by the build system to
DESTDIR). I need a way to map /tmp/foo -> /tmp/foo.dwo by reading .debug_str
from /tmp/foo.
(The reason being: I might have a lot of binaries in my DESTDIR. I need to know
which of them have debug information available & where it is, so I can copy
them into the DESTDIR too in e.g. /usr/lib/debug).
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug general/31287] 0.190: test suite build fails with gcc 14.x
https://sourceware.org/bugzilla/show_bug.cgi?id=31287 --- Comment #1 from Sam James --- Fixed in https://sourceware.org/git/?p=elfutils.git;a=commit;h=ae580d48278b9924da7503886b37be34378e1b04, just needs a new release before 14 is out (or we get mjw to change his mind on werror for releases finally :p) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/32527] elfutils build warnings when building GCC -O3
https://sourceware.org/bugzilla/show_bug.cgi?id=32527 --- Comment #1 from Sam James --- (In reply to Phi from comment #0) > Since we have little chance to get the lexer skeleton fixed from flex team, > a possible workaround is to add the option -Wno-null-dereference in the file > elfutils/libcpu/Makefile.am like this > Please file a bug with flex first if it isn't fixed on master (a lot of changes are in flex master compared to the last release). -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/32930] compile failure in i386_init.c asm/perf_regs.h: No such file or directory
https://sourceware.org/bugzilla/show_bug.cgi?id=32930 Sam James changed: What|Removed |Added CC||matoro_bugzilla_glibc@mator ||o.tk, sam at gentoo dot org See Also||https://bugs.gentoo.org/sho ||w_bug.cgi?id=955065 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/32930] compile failure in i386_init.c asm/perf_regs.h: No such file or directory
https://sourceware.org/bugzilla/show_bug.cgi?id=32930 --- Comment #1 from Sam James --- Ditto alpha: https://bugs.gentoo.org/955065. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/23732] Test failures on sparc64-linux-gnu
https://sourceware.org/bugzilla/show_bug.cgi?id=23732 Sam James changed: What|Removed |Added See Also||https://sourceware.org/bugz ||illa/show_bug.cgi?id=26236 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/23732] Test failures on sparc64-linux-gnu
https://sourceware.org/bugzilla/show_bug.cgi?id=23732 Sam James changed: What|Removed |Added See Also|https://sourceware.org/bugz | |illa/show_bug.cgi?id=26236 | -- You are receiving this mail because: You are on the CC list for the bug.
[Bug libdw/30077] Duplicate definition of typedef struct debuginfod_client in libdwfl
https://sourceware.org/bugzilla/show_bug.cgi?id=30077 Sam James changed: What|Removed |Added CC||sam at gentoo dot org --- Comment #2 from Sam James --- These issues sometimes appear with -flto -Wlto-type-mismatch but not clear that's the case here. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug libdw/30272] Unwinding multithreaded musl applications fails
https://sourceware.org/bugzilla/show_bug.cgi?id=30272 Sam James changed: What|Removed |Added CC||sam at gentoo dot org --- Comment #2 from Sam James --- See also https://marc.info/?l=musl&m=168023060722100&w=2. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug libelf/30729] elf_scncnt: undefined version: ELFUTILS_1.0 during linking phase of libelf.so
https://sourceware.org/bugzilla/show_bug.cgi?id=30729 Sam James changed: What|Removed |Added CC||sam at gentoo dot org --- Comment #1 from Sam James --- (In reply to Kostadin Shishmanov from comment #0) > Steps to reproduce: > > 1. autoreconf -vfi > 2. ./configure --enable-maintainer-mode --disable-debuginfod > 3. export LDFLAGS="-Wl,--no-undefined-version" > 4. make > To be clear, the reason that this is an interesting flag (and why OP is testing this) is because LLD 16 made it default for a bit (then reverted it) and LLD 17 will be setting it too. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug libelf/30729] Build failure with upcoming LLD 17 (elf_scncnt: undefined version: ELFUTILS_1.0 during linking phase of libelf.so)
https://sourceware.org/bugzilla/show_bug.cgi?id=30729 Sam James changed: What|Removed |Added Summary|elf_scncnt: undefined |Build failure with upcoming |version: ELFUTILS_1.0 |LLD 17 (elf_scncnt: |during linking phase of |undefined version: |libelf.so |ELFUTILS_1.0 during linking ||phase of libelf.so) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug libelf/30729] Build failure with upcoming LLD 17 (elf_scncnt: undefined version: ELFUTILS_1.0 during linking phase of libelf.so)
https://sourceware.org/bugzilla/show_bug.cgi?id=30729 Sam James changed: What|Removed |Added See Also||https://bugs.gentoo.org/sho ||w_bug.cgi?id=913112 -- You are receiving this mail because: You are on the CC list for the bug.
