Hi, the valgrind branch is not ready yet. And it grew to 8 patches in the meantime: http://repo.or.cz/w/git/dscho.git?a=log;h=c9486d38d070fefe39f90512e2e12d3a64eba1b3 There is one big problem I only realized today, when trying to catch that valgrind bug [*1*]: in the suppression file, I introduced the "..." notation, which is only available with valgrind 3.4.0. Which was published this month. So I have to think about the issue a bit more, and maybe just claim that valgrind 3.4.0 is required. But maybe there are people who disagree with me saying that older valgrind should be supported. Ciao, Dscho [*1*] Turns out that the issue I was reporting happens with Ubuntu's zlib, which I erroneously thought would be pretty vanilla. It is not: it was compiled with "-O3 -DUNALIGNED_OK", both of which are required to hit the bug. Still, it is a bug in valgrind, I am pretty sure by now, as the byte is not uninitialized as valgrind claims. Oh, and I wasted a _lot_ of time on this today. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
