On Sat, Feb 14, 2009 at 09:33:27PM +0000, Jeremy Henty wrote:
On Sat, Feb 14, 2009 at 05:04:27PM -0300, Jorge Arellano Cid wrote:
On Sat, Feb 14, 2009 at 06:35:48PM +0000, Jeremy Henty wrote:
For your information.
http://starurchin.org/dillo/valgrind.html
It lists the valgrind errors from my most recent Dillo sessions. It's just one big static HTML page at the moment. Feel free to suggest how it could be more useful.
One URL that reproduces each leak would be very helpful.
Would having a single page with anchors for each link be enough, or do you want separate pages for each one?
A single page seems easier.
Repeated leaks can be omitted.
It should already be doing that. I extract the suppression (the part in { ... }) and eliminate duplicates based on that. It's not perfect because different code paths may trigger the same error. I'm hoping it proves to be good enough. I can't see an easy way to do better. Suggestions are welcome.
Usually when fixing one of these bugs, a few others dissappear. But you're right is hard to tell before the fix. You can erase the ones belonging to FLTK. -- Cheers Jorge.-