Jonathan Nieder <jrnieder@xxxxxxxxx> writes: > Even better would be to exit() instead of returning from cmd_ > functions. Valgrind will not consider any memory that still has a > pointer to it at exit time as a leak. Hmm, is there a way to tell valgrind that in these functions pretend as if they left the scope by calling exit() when they return? -- 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