25 Sep
2012
25 Sep
'12
12:51 p.m.
Henning Thielemann wrote:
I also asked in the valgrind mailing list and got this answer: http://sourceforge.net/mailarchive/forum.php?thread_name=506089CA.5030309%40...
Of course, I can suppress the message for me, but I expect that more people will stumble on it. Thus I'd prefer a resolution of the problem in ALSA.
If we worked around this bug in valgrind, then it would not be possible to detect an actual uninitialized-use bug on this variable with a (correctly-working) memory checker.
Regards, Clemens