https://bugs.kde.org/show_bug.cgi?id=458915
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|REPORTED |RESOLVED
--- Comment #27 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
(In reply to David Vasek from comment #26)
> I work on this issue together with Libor. If you checkout this branch:
> https://gitlab.nic.cz/knot/knot-dns/-/commits/valgrind_vgdb_bug , it
> includes a few changes that should help you with the debugging.
Thanks for the above.
With this, I was able to identify the likely culprit for the bug.
I have pushed a fix for this as 348775f34
The valgrind regression tests were run on debian/amd64, centos/ppc64 and
ubunty/arm64.
Also, the ctl/valgrind knot test has run 80 times without encountering the
abort
(while before the fix, each run of ctl/valgrind was triggering the bug).
It would be nice if you could check with the latest state of the git repository
if everything works
as expected now.
Thanks for the clear and detailed instructions to reproduce the bug, which was
critically needed to
reproduce this race condition.
--
You are receiving this mail because:
You are watching all bug changes.
