Comment #7 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
Before we continue on this, is there a chance for you to use gcc 4.9? This
has many usability improvements compared to 4.8.
When you mentioned LD_PRELOAD, did you mean the instructions
at https://code.google.com/p/address-sanitizer/wiki/AsanAsDso?
Yes, more or less.
Also is there a tool to find out which module maps to the addresses
such as '0x000096e00000'?
I guess it's not a module but rather some anonymous mapping coming from
malloc or maybe JVM is directly mmapping buffers for internal use. You can
run under gdb and break on mmaps/mallocs to find out.
#0 0x7f9b8fec2b6b (/usr/lib64/libasan.so.0.0.0+0xab6b)
Running addr2line on these addresses may help to understand what's going on.
--
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.
