Josip Rodin wrote: > That just doesn't seem safe enough when an analogous bit of parsing code in > cf_section_parse() does: .. > and cf_item_parse() can fail, so it stands to reason that *data can > remain unwritten, and should not be free()'d.
The solution is to write to data. The reason is that the parse routing may parse *many* configuration entries correctly, before running into an error. To avoid a memory leak, the pointers should be initialized before they are used. I've committed a change to the v2.1.x branch which fixes this. Alan DeKok. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
