Don Zickus <dzickus@xxxxxxxxxx> writes: > Recent changes to is_multipart_boundary() caused git-mailinfo to segfault. > The reason was after handling the end of the boundary the code tried to look > for another boundary. Because the boundary list was empty, dereferencing > the pointer to the top of the boundary caused the program to go boom. We keep fixing and breaking this thing, don't we? Can we have a testcase to protect this codepath? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
