Would you be able to implement a software version of this (especially 64bit), it picks up the different forms of memory corruption with a single check.
https://android-developers.googleblog.c ... wasan.html
"SWASAN" like android used to use.
with a build you have to select under run or overrun so have to do twice as many checks while using the software to pickup this kind of error.
ASAN handles all these situations so would be a big advantage.
Yes, it's true that you have to decide whether to check for buffer overruns or underruns, you can' test for both at the same time. However, buffer underruns are quite rare, compared to buffer overruns.
Overall, I don't see the big benefit of switching to ASAN compared to what I already have. I'm not even sure if ASAN raises exceptions in the moment when the buffer overrun occurs? The documentation isn't very clear on that. It's quite possible that it only detects buffer overruns after the fact (e.g. in the moment when you free the buffer). If that's the case, it would actually be a noticeably inferior solution compared to what madExcept does.
To sum up: Porting over an Android solution to Windows would probably very time consuming, and considering that there are only small improvements to be had (and potentially it could even be a worse solution!), it doesn't really seem to be worth the effort, from what I can see right now.