Re: [PATCH 2/2] libdw: Use elf_rawdata when checking .debug section

Hi, On Tue, 2023-02-21 at 05:28 +0300, Evgeny Vereshchagin wrote: > On Mon, 20 Feb 2023 at 19:03, Aleksei Vetrov wrote: > > On Mon, Feb 20, 2023 at 3:55 PM Mark Wielaard wrote: > > > > > > .debug sections are raw bytes and don't need conversion even when host > > > and file have different endia

Re: [PATCH] libasm: Fix use-after-free issue with circular single linked list cleanup

Hi, On Fri, 2023-02-17 at 15:00 +0100, Mark Wielaard wrote: > Pointed out by gcc 12 with -Wuse-after-free=3 > > In function ‘free_section’ > asm_end.c:552:17: error: pointer ‘data’ used after ‘free’ > [-Werror=use-after-free] > 552 | while (oldp != scnp->content); > |

☺ Buildbot (Sourceware): elfutils - build successful (master)

A restored build has been detected on builder elfutils-rawhide-x86_64 while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#builders/140/builds/117 Build state: build successful Revision: eb79a7bd87adc51dae77eb8d5ec37ad58ec71feb Worker: bb2-2 Build

☺ Buildbot (Sourceware): elfutils - build successful (master)

A restored build has been detected on builder elfutils-gentoo-sparc while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#builders/225/builds/33 Build state: build successful Revision: c9c055a6949702af57e46f4eac3355d4a4f94c5d Worker: gentoo-sparc Bu

elfutils 0.189 release next week

Hi, We accumulated a lot of patches since 0.188 (59 commits by 13 authors) with some nice new features and some important bug fixes. So it would be good to push a new release out. I cleaned up the patchwork list and will go over the following 25 pending patches to see what can be incorporated: ht

Re: elfutils code names

On Thu, 2023-02-16 at 13:37 +0100, Mark Wielaard wrote: > Hi, > > On irc (#elfutils on libera.chat) we had a discussion about the > elfutils code names. For some reason those are only in the irc channel > topic. Which seems to mean not many people know about them. I could > recover the following:

Issue 56134 in oss-fuzz: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in check_section

Updates: Labels: -Reproducible Unreproducible Comment #3 on issue 56134 by ClusterFuzz-External: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in check_section https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56134#c3 ClusterFuzz testcase 6724057145147392 appears to be flaky, up

[Bug libdw/30085] Negative strides in dwarf_aggregate_size

https://sourceware.org/bugzilla/show_bug.cgi?id=30085 --- Comment #2 from Mark Wielaard --- I asked around and John DelSignore came up with the following fortran example: = array.f95 = program f_prog integer*4, allocatable, target, dimension (:,:) :: big_array integer, dimension

Re: [PATCH 2/2] libdw: Use elf_rawdata when checking .debug section

Hi Evgeny, On Tue, Feb 21, 2023 at 2:29 AM Evgeny Vereshchagin wrote: > Aleksei I wonder if it would be possible to add those fuzz targets to > OSS-Fuzz? There are blind spots there and I think it would be really great to > start covering at least some of them. We are fuzzing a tool named STG (h

[Bug libdw/30085] Negative strides in dwarf_aggregate_size

https://sourceware.org/bugzilla/show_bug.cgi?id=30085 --- Comment #3 from Tim Haines --- I was actually trying to make a Fortran example, but couldn't get one to work! Glad John was able to make one. -- You are receiving this mail because: You are on the CC list for the bug.

[COMMITTED] Update m4 files from autoconf-archive

Update m4/ax_check_compile_flag.m4 and m4/ax_cxx_compile_stdcxx.m4 to autoconf-archive-2023.02.20. Signed-off-by: Mark Wielaard --- m4/ax_check_compile_flag.m4 | 33 +-- m4/ax_cxx_compile_stdcxx.m4 | 532 +--- 2 files changed, 503 insertions(+), 62 deletions(-)