https://bugs.kde.org/show_bug.cgi?id=458915
David Vasek <david.va...@nic.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |david.va...@nic.cz
--- Comment #26 from David Vasek <david.va...@nic.cz> ---
(In reply to Philippe Waroquiers from comment #25)
> Is there an easy change to the test framework that would ensure all the
> output is either in stderr or valgrind file ?
Hello Philippe,
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.
1. All output from valgrind is written to knot1/stderr (the split output you
saw before was apparently made by valgrind when option `--log-file` was used).
2. The options for valgrind you have suggested are already set in the
framework. If you need to change them, it's obvious from the last commit where
they are.
3. There is a new "test" `ctl/valgrind` that is simple and triggers the bug
very fast. You can run it as `./runtests.py ctl/valgrind` from
knot-dns/tests-extra, same as the test before.
4. When knotd encounters the bug, it calls abort now. Then it's easy to find
the place in the valgrind output (knot1/stderr) by searching for 'abort'. If
you don't need it, you remove the two asserts added in the last commit.
--
You are receiving this mail because:
You are watching all bug changes.
