On Thu, Jan 31, 2013 at 09:22:52PM -0500, Daniel Kahn Gillmor wrote: > FWIW, in the existing API, it's not clear who is responsible for > allocating or disposing of the memory referred to by > response->message. This has worked without failure thus far because > the memory was just staying allocated (and leaking). > > Clarifying the responsibility for tracking the memory allocation for > response->message would help in figuring out the right way to deal > with the above bugs.
Other than addressing this bit, fixes have been pushed to master. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
