On Sun, 8 Jun 2014, Luca Barbato wrote:
On 08/06/14 00:55, Martin Storsjö wrote:
However, valgrind's memcheck tool intentionally assumes that the
redzone is clobbered on every function call and function return
(see a long comment in valgrind/memcheck/mc_main.c). This avoids
false positives in that tool, at the cost of an extra stack pointer
adjustment.
I'm fine with that, people reporting the issue to valgrin by providing a
patch would be welcome but I doubt anybody has time.
Well, given how much this is exactly how they've intended it to behave, I
doubt they'd be willing to accept a patch that "fixes" it, since it would
probably silence detection of a whole lot of other issues instead. That's
why I didn't even try to make such a patch, once I found that explanation.
// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
