On Sun, Feb 15, 2009 at 09:17:09AM -0300, Jorge Arellano Cid wrote:
But, I miss the URL to reproduce the BUG. That's what I meant in the previous email; please excuse me if it wasn't clear.
Oh, I see. Unfortunately I don't have that information, the code just parses the output of Valgrind. When an error occurs there is no indication which of the current pages produced it. Worse, valgrind only reports leaks after the program exits. I haven't been able to find a specific example that reproduces any of these problems. I strongly suspect that the errors we are seeing now are non-deterministic and come from race-like conditions between different pages. Every time I run dillo on a single page the valgrind report is clean. Maybe there's some deep valgrind magic that would yield more information, but if so I don't know of it. Any ideas? Regards, Jeremy Henty