You don't need reviews.llvm.org,
please follow https://code.google.com/p/address-sanitizer/wiki/HowToContribute

By ARM, do you mean ARM Linux? 

Yes, we do.

Done to llvm-commits@cs.uiuc.edu.

Am I understanding right that this is 32-bit ARM?
If so, have you tested this patch on any sufficiently big app?

The problem with 32-bit architectures is that a random 32-bit number is very likely
to be treated as a pointer to some existing allocation. This may lead to false negatives
in leak detection.
In fact that's why there's no 32-bit x86 LSan.

Yes, that's 32-bit ARM Linux

The most complicated code that we've tested was bash, it works fine with LSan. Is it
enough big or maybe we should test some bigger apps? Do you have any suggestions? 

using 32-bit leak detector becomes painful after some period of deployment, 
as we've learned in a hard way.
The major trouble is that the leak detector has lots of flaky false negatives
(missed leaks)
https://code.google.com/p/valgrind-variant/wiki/LeakCheckingOn32bits

If you have a choice to use AArch64 instead of ARM for leak detection, go for it.
If no, then, well, we've warned you. :) 

Hm, you are actually right - LSan on ARM only finds about 15% of leaks. The results
are close to valgrind's on x86 so we decided to halt our work.

I think we can close this issue.

Adding Project:AddressSanitizer as part of GitHub migration.