Comment #1 on issue 386 by [email protected]: JNI-based app fails with
shadow memory range interleaves with existing memory mapping after ASan
instrumentation
https://code.google.com/p/address-sanitizer/issues/detail?id=386
These guys are in the shadow gap. Any idea where they come from?
0x000096e00000-0x000098350000
0x000098350000-0x00009c000000
0x00009c000000-0x0000c5d90000
0x0000c5d90000-0x0000deab0000
0x0000deab0000-0x000100000000
// Typical shadow mapping on Linux/x86_64 with SHADOW_OFFSET ==
0x00007fff8000:
// || `[0x10007fff8000, 0x7fffffffffff]` || HighMem ||
// || `[0x02008fff7000, 0x10007fff7fff]` || HighShadow ||
// || `[0x00008fff7000, 0x02008fff6fff]` || ShadowGap ||
// || `[0x00007fff8000, 0x00008fff6fff]` || LowShadow ||
// || `[0x000000000000, 0x00007fff7fff]` || LowMem ||
If you are OK with patching the compiler, mapping can be changed. See
AddressSanitizer.cpp and asan_mapping.h (compiler-rt).
It looks like increasing the offset (currently 0x00007fff8000) could help.
But it's very unlikely to be accepted upstream.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
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.
