Hi, First of all, why would you want to do such thing? > Do you have a particular use case? >
It's a justified question. We do have use cases for this. For example, consider a library that is formally proven to be free from memory errors. We can already build this library without ASan, so that it won't have checks. Yet it is still linked with the ASan memory allocator, so its objects have red zones, compete for quarantine space, etc. There are other questions to clarify, like how to separate the unsafe memory space from the regular program memory. But I think we could solve these in time when they arrive. For now, I'm looking mostly for ideas about how unprotected objects could coexist with ASan. Cheers, Jonas -- 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.
