Buildbot failure in Wildebeest Builder on whole buildset

2021-09-06 Thread buildbot
The Buildbot has detected a new failure on builder elfutils-debian-i386 while building elfutils. Full details are available at: https://builder.wildebeest.org/buildbot/#builders/4/builds/813 Buildbot URL: https://builder.wildebeest.org/buildbot/ Worker for this Build: debian-i386 Build

Buildbot failure in Wildebeest Builder on whole buildset

2021-09-06 Thread buildbot
The Buildbot has detected a new failure on builder elfutils-debian-armhf while building elfutils. Full details are available at: https://builder.wildebeest.org/buildbot/#builders/15/builds/607 Buildbot URL: https://builder.wildebeest.org/buildbot/ Worker for this Build: debian-armhf Build

Re: Buildbot failure in Wildebeest Builder on whole buildset

2021-09-06 Thread Mark Wielaard
Hi, On Mon, Sep 06, 2021 at 10:02:11PM +0200, Mark Wielaard wrote: > Still looking for explanations of the other FAILS (which I cannot > reproduce locally). I think I finally got it. The thing that all the tests that are (sometimes) failing have in commen is that they use SIGUSR1 or SIGUSR2 to

[COMMITTED] tests: Only export DEBUGINFOD_URLS when necessary

2021-09-06 Thread Mark Wielaard
A couple of test set DEBUGINFOD_URLS before starting a debuginfd server causing the server to query itself or a nonexisting debuginfod server as delegate. In most cases it should be set after, except for the testcase that explicitly checks for errors when using an invalid URL. Signed-off-by: Mark

Buildbot failure in Wildebeest Builder on whole buildset

2021-09-06 Thread buildbot
The Buildbot has detected a new failure on builder elfutils-fedora-x86_64 while building elfutils. Full details are available at: https://builder.wildebeest.org/buildbot/#builders/3/builds/814 Buildbot URL: https://builder.wildebeest.org/buildbot/ Worker for this Build: fedora-x86_64 Build

Re: Buildbot failure in Wildebeest Builder on whole buildset

2021-09-06 Thread Mark Wielaard
On Mon, Sep 06, 2021 at 10:02:11PM +0200, Mark Wielaard wrote: > This doesn't really explain the above failures, but there were still > two tests that didn't use their own debuginfod client cache. Also one > set a useless, but confusing DEBUGINFOD_URLS. > > Still looking for explanations of the

Re: Buildbot failure in Wildebeest Builder on whole buildset

2021-09-06 Thread Mark Wielaard
Hi, On Mon, Sep 06, 2021 at 05:07:50PM +0200, Mark Wielaard wrote: > On Sat, 2021-09-04 at 01:47 +0200, Mark Wielaard wrote: > > On Fri, Sep 03, 2021 at 02:08:40PM +, > > build...@builder.wildebeest.org wrote: > > > The Buildbot has detected a new failure on builder elfutils-debian- > > >

[PATCH] findtextrel: do not use unbound alloca

2021-09-06 Thread Dmitry V. Levin
This fixes the following compilation warning: findtextrel.c:184:1: warning: stack usage might be unbounded [-Wstack-usage=] Signed-off-by: Dmitry V. Levin --- src/ChangeLog | 5 + src/Makefile.am | 1 - src/findtextrel.c | 31 +-- 3 files changed, 14

Re: Buildbot failure in Wildebeest Builder on whole buildset

2021-09-06 Thread Mark Wielaard
On Sat, 2021-09-04 at 01:47 +0200, Mark Wielaard wrote: > On Fri, Sep 03, 2021 at 02:08:40PM +, > build...@builder.wildebeest.org wrote: > > The Buildbot has detected a new failure on builder elfutils-debian- > > armhf while building elfutils. > > Full details are available at: > >

[PATCH 2/2] Use xasprintf instead of asprintf followed by error(EXIT_FAILURE)

2021-09-06 Thread Dmitry V. Levin
Signed-off-by: Dmitry V. Levin --- lib/ChangeLog | 3 +++ lib/color.c | 6 ++ src/ChangeLog | 7 +++ src/objdump.c | 17 - src/readelf.c | 14 ++ src/unstrip.c | 8 ++-- 6 files changed, 28 insertions(+), 27 deletions(-) diff --git a/lib/ChangeLog

[PATCH 1/2] Introduce xasprintf

2021-09-06 Thread Dmitry V. Levin
Similar to other x* functions, xasprintf is like asprintf except that it dies in case of an error. Signed-off-by: Dmitry V. Levin --- lib/ChangeLog | 6 ++ lib/Makefile.am | 2 +- lib/libeu.h | 2 ++ lib/xasprintf.c | 52 + 4 files

[PATCH] Remove redundant casts of memory allocating functions returning void *

2021-09-06 Thread Dmitry V. Levin
Return values of functions returning "void *", e.g. calloc, malloc, realloc, xcalloc, xmalloc, and xrealloc, do not need explicit casts. Signed-off-by: Dmitry V. Levin --- debuginfod/ChangeLog | 5 + debuginfod/debuginfod-client.c | 2 +- lib/ChangeLog|