On Fri, May 22, 2009 at 02:31:58PM -0400, Jorge Arellano Cid wrote:
On Tue, May 19, 2009 at 07:34:30AM +0100, Jeremy Henty wrote:
I have just applied a patch I was considering earlier that makes a_Cache_stop_client() close the client.
And now I have just unapplied it because it crashed Dillo all the time. <sigh> If this patch isn't wrong, then something else is.
A huge step forward would be to find a way to repoduce the bug.
Believe me, I know. Unfortunately my current patches do little more than confirm at the end of the session that sometime previously, something, somewhere went wrong. Which is great for confirming the existence of the bug, but for fixing it, not so much. What's really needed is complete logging of the CCC, the cache and the dicache. Back to the drawing board...
My guess is that this semantic is still fuzzy ...
It's nice to know that it isn't just me who doesn't understand the code! :-) Just what is a repush anyway? (BTW, I'm not complaining, just pining for the good old days when Dillo was so buggy that it was easy for me to find something I could actually fix. :-) :-) ) Regards, Jeremy Henty PS. I agree that this should not block Dillo-2.1 . Just think of it as the Moby Dick to my Captain Ahab. From Hell's heart I stab at thee, freed struct DilloImage! Dillo-2.1 *will* rock, whether or not this is fixed.