Junio C Hamano wrote:
Jonathan Nieder [off-list ref] writes:
quoted
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?
You mean a way to tell it to trap the return from these functions?
No, I don't think so.