[Bug libelf/29000] New: Conditional jump or move depends on uninitialised value in elf_compress_gnu

https://sourceware.org/bugzilla/show_bug.cgi?id=29000 Bug ID: 29000 Summary: Conditional jump or move depends on uninitialised value in elf_compress_gnu Product: elfutils Version: unspecified Status: UNCONFIRMED

[PATCH 3/3] elflint: Recognize NT_FDO_PACKAGING_METADATA

Signed-off-by: Mark Wielaard --- src/ChangeLog | 4 src/elflint.c | 7 +++ 2 files changed, 11 insertions(+) diff --git a/src/ChangeLog b/src/ChangeLog index 0e705b7d..1e3c31a8 100644 --- a/src/ChangeLog +++ b/src/ChangeLog @@ -1,3 +1,7 @@ +2022-03-24 Mark Wielaard + + * elflin

[PATCH 2/3] libebl: recognize FDO Packaging Metadata ELF note

From: Luca Boccassi As defined on: https://systemd.io/COREDUMP_PACKAGE_METADATA/ this note will be used starting from Fedora 36. Allow readelf --notes to pretty print it: Note section [ 3] '.note.package' of 76 bytes at offset 0x2e8: Owner Data size Type FDO 57 F

[PATCH 1/3] libelf: Sync elf.h from glibc.

Adds EM_INTELGT, NT_ARM_TAGGED_ADDR_CTRL, NT_ARM_PAC_ENABLED_KEYS, ELF_NOTE_FDO, NT_FDO_PACKAGING_METADATA and OpenRISC 1000 specific relocs. It also adds and renames some GNU_PROPERTY constants. But none of the constants the elfutils code uses was renamed or given a different constant value. dwe

Re: [PATCH v2] libebl: recognize FDO Packaging Metadata ELF note

> I haven't forgotten about this. The glibc elf.h change has been > integrated now. But when I wanted to resync with the elfutils > libelf/elf.h version I noticed something that look like ABI > breakage: > https://sourceware.org/pipermail/libc-alpha/2021-December/133589.html > > I am trying to get

Issue 45633 in oss-fuzz: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in __libelf_read_mmaped_file

Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 45633 by ClusterFuzz-External: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in __libelf_read_mmaped_file https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45633#c1 ClusterFuzz testcase 62985519891

Issue 45631 in oss-fuzz: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in __libdw_gunzip

Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 45631 by ClusterFuzz-External: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in __libdw_gunzip https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45631#c4 ClusterFuzz testcase 5742116662280192 is ve

Issue 45630 in oss-fuzz: elfutils:fuzz-libelf: Use-of-uninitialized-value in validate_str

Updates: Labels: -Reproducible Unreproducible Comment #5 on issue 45630 by ClusterFuzz-External: elfutils:fuzz-libelf: Use-of-uninitialized-value in validate_str https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45630#c5 ClusterFuzz testcase 5658767587409920 appears to be flaky, upda

Get r_debug from a core file

Hi, I'm trying to obtain the r_debug structure from a core file. It seems that elfutils is able to obtain the structure using the "dwfl_link_map_report" function, but unfortunately this is internal. Is there a known way to obtain the structure using functions from the public API? If not, would y

[Bug libdw/24158] run-backtrace-native-biarch.sh test fails on CC='gcc -m32' CXX='g++ -m32' x86_64 host.

https://sourceware.org/bugzilla/show_bug.cgi?id=24158 --- Comment #3 from Mark Wielaard --- This disables the "biarch" tests in the case of a 32bit build. commit d85945f1056641180e03fb48ab770b893125786e Author: Mark Wielaard Date: Mon Mar 21 00:34:24 2022 +0100 configure: Don't check whe

Re: [PATCH] configure: Don't check whether -m64 works for 32bit host biarch check

On Mon, Mar 21, 2022 at 12:47:51AM +0100, Mark Wielaard wrote: > Running a 32bit backtrace test against a 64bit binary doesn't work. > Only a 64bit binary can backtrace a 32bit binary. So disable the > biarch check that inserts -m64 for a 32bit host. Pushed. Mark

[Bug general/28975] run-large-elf-file.sh fails in 32-bit cross-compile on 64-bit machine

https://sourceware.org/bugzilla/show_bug.cgi?id=28975 Mark Wielaard changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

Re: [PATCH] tests: Check addsections test binary is 64bit for run-large-elf-file.sh

On Mon, Mar 21, 2022 at 12:17:14AM +0100, Mark Wielaard wrote: > The test binary should be 64bit to be able to create 4GB, or larger, > ELF files. Pushed. Mark