2009/12/26 Randi Botse <nightdecoder@xxxxxxxxx>: > Hi Vinit, > > So, does this function actually reentrant when free() has not been > called?, thanks for your explanation. This function is reentrant both when free(3) is called and when free(3) is not called (but it introduce memory leaks in the second case). As I've written before, the only issue may be with printf(3) as output from various threads may get mixed together. -- To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
