Comment #14 on issue 278 by [email protected]: Do not sanitize kernel
area on 32-bit targets
http://code.google.com/p/address-sanitizer/issues/detail?id=278
Ok, mmap trick didn't work for (it looks like kernel does not respect
address hint deeply enough). All other tricks are rather unstable as well.
I think the core problem with schroot is that it sets non-trivial
personality. We should be able to detect this (by checking return value of
personality(-1)) and leave default 4G limit unchanged.
--
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.
