On Fri, Jun 5, 2015 at 9:32 PM, Yuri Gribov <[email protected]> wrote:
> On Fri, Jun 5, 2015 at 9:12 PM, 'Alexey Samsonov' via address-sanitizer < > [email protected]> wrote: > >> Looks like the position of Java heap (0xdfff8000) interferes with ASan >> shadow memory mappings. >> See memory layout in projects/compiler-rt/lib/asan/asan_mapping.h. >> >> __asan_region_is_poisoned arguments seem to be a red herring - it's >> possible that debug info is incorrect. >> > > Indeed, they would cause a segfault if they were real, contrary to the > original error report (unknown-crash at 0x0000dfff8000). It seems that > someone (JVM?) spoils ASan shadow memory which later drives ASan crazy. > > @Dima: ASan should have printed shadow memory contents after the > backtrace, could you post it as well? > If ASan intecepted mmap, it could detect errors like this. -Y -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
