Re: Buildbot failure in Wildebeest Builder on whole buildset

2021-10-18 Thread Mark Wielaard
Hi, On Mon, 2021-10-18 at 13:45 +, build...@builder.wildebeest.org wrote: > The Buildbot has detected a new failure on builder elfutils-debian- > amd64 while building elfutils. > Full details are available at: > https://builder.wildebeest.org/buildbot/#builders/2/builds/841 > > Buildbot U

Buildbot failure in Wildebeest Builder on whole buildset

2021-10-18 Thread buildbot
The Buildbot has detected a new failure on builder elfutils-debian-amd64 while building elfutils. Full details are available at: https://builder.wildebeest.org/buildbot/#builders/2/builds/841 Buildbot URL: https://builder.wildebeest.org/buildbot/ Worker for this Build: debian-amd64 Build Re

[COMMITTED] libdw: Don't pass NULL to dwarf_peel_type

2021-10-18 Thread Mark Wielaard
commit c3a6a9dfc "libdw: Use signedness of subrange type to determine array bounds" introduced a type check on a DIE which exposed a latent bug in the get_type function. Even if the type of a DIE couldn't be determined it would call dwarf_peel_type on it. The gcc undefined sanitizer would flag this

[Bug libdw/28294] dwarf_aggregate_size fails on some array types

2021-10-18 Thread mark at klomp dot org via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=28294 Mark Wielaard changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libdw/28294] dwarf_aggregate_size fails on some array types

2021-10-18 Thread mark at klomp dot org via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=28294 --- Comment #4 from Mark Wielaard --- Pushed as: commit c3a6a9dfc6ed0c24ab2d11b2d71f425b479575c9 Author: Mark Wielaard Date: Wed Oct 6 22:41:29 2021 +0200 libdw: Use signedness of subrange type to determine array bounds When calc

Re: [PATCH] debuginfod-client: Stick to http:// + https:// + file:// protocols

2021-10-18 Thread Mark Wielaard
Hi, On Fri, 2021-10-15 at 15:25 +0200, Mark Wielaard wrote: > Make sure we don't use any of the more experimental protocols > libcurl might support. URLs can be redirected and we might want > to follow http -> https, but not e.g. gopher or pop3. On irc Frank said he didn't have any objections to