[asterisk-dev] Locking in astmm.c

[Kevin P. Fleming]

Matt Roth wrote:

> Does my change look safe, or am I introducing a race condition?

Short answer: don't touch it.

Long answer: this codes lives underneath ast_malloc() if MALLOC_DEBUG is 
defined, and should not ever call ast_malloc itself. It is _not_ called 
directly, and has no need for generating log messages about allocation 
failures, since its caller will do that.