read after free in notmuch new
david at tethera.net
Sun Feb 19 07:29:53 PST 2017
David Bremner <david at tethera.net> writes:
> I haven't had a chance to really track this down, but it seems there is
> a memory error in notmuch new (or a maybe false positive from valgrind).
> Attached is the log from running "make memory-test OPTIONS=--medium" on
> current git master (0e037c34).
> It looks like we talloc the message_id string with the message object as
> parent, but it somehow outlives the message object.
Sorry, that had a few commits beyond master.
master (08343d3d) gives essentially the same log.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 32040 bytes
Desc: not available
More information about the notmuch