[Bug libdw/32713] elfutils fails to symbolize core dumps created by Linux 6.12+
https://sourceware.org/bugzilla/show_bug.cgi?id=32713 --- Comment #4 from Brian Mak --- (In reply to Mark Wielaard from comment #2) > See also this kernel thread: > https://lore.kernel.org/all/39fc2866-dff3-43c9-9d40-e8ff30a21...@juniper.net/ > Looks like the kernel people believe this in "in spec" so doesn't really > break user space handling. So we'll have to figure out to work around it > somehow. Per that reply, we are actually out of spec. I'm working on a patch to bring us back into spec, while still maintaining a sorted VMA size ordering. Meanwhile, a separate patch is being worked up to gate the VMA sorting behind a sysctl. The part that is out of spec is the fact that the program headers are also written in VMA size order. Loadable segments must be specified in virtual memory ordering in the program header table, per the ELF specs: "Loadable segment entries in the program header table appear in ascending order, sorted on the p_vaddr member." Hope this clears things up. -- You are receiving this mail because: You are on the CC list for the bug.
Re: [obv] [patch] debuginfod-client memory hygiene
Hi - > [...] > This does sounds like a bug in glibc sscanf. I cannot find a > description of what exactly happens with 'm' modifier allocated > buffers on error. So I can imagine a double free if sscanf frees the > buffer on error. But returning a bogus pointer? That seems a bug. If > we aren't guaranteed a valid pointer (or NULL) then this could easily > lead to memory leaks. Spent way too long trying to reproduce this. It was a PEBCAK on my part, comparing a version of elfutils with the distro, and a locally-built one that included this commit. I think I must have mixed up some LD_LIBRARY_PATH and run a franken-binary, then misplaced the blame for the crash. I'll revert my unnecessary fix. (It might be nice if the fedora build got this fix sometime.) commit 1be0787d6654ed71bf659e8bfd34895fea7589eb Author: Aaron Merey Date: Fri Jan 24 19:43:19 2025 -0500 debuginfod-client.c: Avoid freeing uninitialized value - FChE
[Bug debuginfod/32318] client should avoid url duplication for different ima:FOO modes
https://sourceware.org/bugzilla/show_bug.cgi?id=32318 Frank Ch. Eigler changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Frank Ch. Eigler --- . -- You are receiving this mail because: You are on the CC list for the bug.
☠ Buildbot (Sourceware): elfutils-snapshots-coverage - failed test (failure) (main)
A new failure has been detected on builder elfutils-snapshots-coverage while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/250/builds/210 Build state: failed test (failure) Revision: e543c7f5c2b28ac2bce1e9f09fad30caebb579d5 Worker: snapshots Build Reason: (unknown) Blamelist: Frank Ch. Eigler Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/1/logs/stdio - 2: autoreconf ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/3/logs/config_log - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/4/logs/stdio - warnings (3): https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/4/logs/warnings__3_ - 5: make check ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/5/logs/stdio - test-suite.log: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/5/logs/test-suite_log - 6: make coverage ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/6/logs/stdio - warnings (5): https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/6/logs/warnings__5_ - 7: Wait snapshots output ready ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/7/logs/stdio - 8: create output ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/8/logs/stdio - 9: create publish file ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/250/builds/210/steps/9/logs/stdio
☠ Buildbot (Sourceware): elfutils - failed test (failure) (main)
A new failure has been detected on builder elfutils-fedora-s390x while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/43/builds/395 Build state: failed test (failure) Revision: e543c7f5c2b28ac2bce1e9f09fad30caebb579d5 Worker: fedora-s390x Build Reason: (unknown) Blamelist: Frank Ch. Eigler Steps: - 0: worker_preparation ( success ) - 1: set package name ( success ) - 2: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/2/logs/stdio - 3: autoreconf ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/3/logs/stdio - 4: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/4/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/4/logs/config_log - 5: get version ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/5/logs/stdio - property changes: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/5/logs/property_changes - 6: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/6/logs/stdio - warnings (3): https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/6/logs/warnings__3_ - 7: make check ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/7/logs/stdio - test-suite.log: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/7/logs/test-suite_log - 8: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/8/logs/stdio - 9: build bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/9/logs/stdio - 10: fetch bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/10/logs/stdio - 11: unpack bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/11/logs/stdio - 12: pass .bunsen.source.* ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/12/logs/stdio - 13: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/13/logs/stdio - 14: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/14/logs/stdio - 15: make distclean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/43/builds/395/steps/15/logs/stdio
[Bug tools/32673] eu-strip SEGV (illegal read access) in gelf_getsymshndx (libelf/gelf_getsymshndx.c:123)
https://sourceware.org/bugzilla/show_bug.cgi?id=32673 xuantong shi changed: What|Removed |Added CC||sxt1001 at outlook dot com --- Comment #4 from xuantong shi --- Sorry, Is elfutils-0.185 affected? I can reproduce the issue in version 0.189, but not in version 0.185. I compared the code and think that the elfutils-0.185 should also be affected, but I don't know why it can't be reproduced -- You are receiving this mail because: You are on the CC list for the bug.
