On Thu Jun 8 16:03:04 2023 +0000, Hans Leidekker wrote:
There's even more, read_dependency() also calls free_dependency() after calling read_identity() indirectly. I think it would be better reset the pointers in clear_identity(), to avoid reintroducing this bug. Please also fix the title. This is a double free, not a memory leak.
Whoops. I fixed the title, but I will have to come back to this when I have time to look at the other double frees you mentioned (hopefully later today). Thanks for the feedback.