http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55517
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> 2012-11-28 12:48:56 UTC --- (In reply to comment #1) > I am quite sure that asan should not mess with the limits itself. > It gets too messy too soon. (e.g. in tsan we try to reexec if the stack is > unlimited, but it's not reliable). Well, raising a soft virtual limit should be straight-forward if you create such large mappings. SLES ships with a default soft virtual limit, and only asan knows how much extra shadow memory it needs. > I agree, the messages could be less cryptic. It btw causes c-c++-common/asan/memcmp-1.c to FAIL in all my tests which is quite annoying because the addresses printed in the message vary and thus testresults are not comparable.
