On 08/19/2014 04:31 PM, Yury Gribov wrote:
On 08/19/2014 03:37 PM, Dominique Dhumieres wrote:
Makes sense, I've attached new patch (retested as usual).
Well, you probably did not test with -m32:
Right, I only did plain "make check" until now. Thanks for reporting,
I'll check this tomorrow.
Looks like the pattern in my test is too strict:
Asan will not always be able to detect that invalid memory access
is use-after-return (see implementation of __asan_poison_memory_region
for details). I'll cook a trivial patch to fix this next week.
-Y
