https://bugs.kde.org/show_bug.cgi?id=511717
--- Comment #5 from Libor Peltan <[email protected]> --- I have no insight to Valgrind internals, therefore I can hardly imagine what "packet" is being decoded there. Anyway, I tried with older Valgrind versions built from git (checkout old tags). I can confirm that the issue appears also (in equal manner) in Valgrind 3.21.0 (possibly also older) and since. What is puzzling me is that I only started experiencing the issue last week after upgrading my Ubuntu. Maybe also some changes in the underlying tested software (Knot DNS) do trigger the bug. I have to apologise, I'll be pretty busy with different agenda next week. However, I'm willing to cooperate on further debugging soon. Do you have any ideas what should we try next? I can make any adjustments to the valgrind code and rebuild and retry any number of times :) What is the most effective ways of debugging valgrind internals? Thank you! -- You are receiving this mail because: You are watching all bug changes.
