Fwd: Buildbot failure in Wildebeest Builder on whole buildset
Mark Wielaard
mark@klomp.org
Thu Mar 25 10:41:20 GMT 2021
Hi Tom,
On Thu, 2021-03-25 at 09:50 +0100, Tom de Vries wrote:
> I've just committed patch "Move hardlink handling out of dwz
> function"
> and there's this buildbot failure.
>
> Is there something easy that you can do to find out if this is a
> fluke
> or not, f.i. retry the build for that bot?
I logged into the buildbot worker and did a dwz build myself.
make check does produce 32 unexpected failures.
Removing the last commit makes everything pass.
Adding the commit again produces the failures again.
It isn't a fluke.
The problem is simply that:
cp hello 1
dwz 1
Makes dwz produce an exit code of 1 which seems to be interpreted as
child process exited abnormally in a make check run.
running under valgrind --track-origins=yes gives:
==31313== Conditional jump or move depends on uninitialised value(s)
==31313== at 0x127974: dwz (dwz.c:15287)
==31313== by 0x10BB7C: dwz_with_low_mem (dwz.c:16227)
==31313== by 0x10BB7C: dwz_one_file (dwz.c:16253)
==31313== by 0x10BB7C: main (dwz.c:16532)
==31313== Uninitialised value was created by a stack allocation
==31313== at 0x10B59B: main (dwz.c:16513)
I haven't tracked down what res->res precisely depends on that doesn't
have a defined value.
Cheers,
Mark
More information about the Dwz
mailing list