git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Status of my valgrind branch

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 30, 2009, 01:19 UTC
Message-ID
<alpine.DEB.1.00.0901300213590.3586@pacific.mpi-cbg.de>
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.
Message 1 of 1 in “Status of my valgrind branch”
  1. Johannes SchindelinJan 30, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.