Dave Reisner abfa8370c0 dload: unhook error buffer after transfer finishes ... Similar to what we did in edd9ed6a, disconnect the relationship with our stack allocated error buffer from the curl handle. Just as an FTP connection might have some network chatter on teardown causing the progress callback to be triggered, we might also hit an error condition that causes curl to write to our (now out of scope) error buffer. I'm unable to reproduce FS#26327, but I have a suspicion that this should fix it. Signed-off-by: Dave Reisner <dreisner@archlinux.org> Signed-off-by: Dan McGee <dan@archlinux.org>		2011-10-10 19:09:59 -05:00
..
libalpm	dload: unhook error buffer after transfer finishes	2011-10-10 19:09:59 -05:00