asan: move the conflict check into its own loop

There was a condition race in which some conflicts would be caught but
sometimes wouldn't depending on how/when `memory.memory_ranges` was
being filled.

Instead of this, just fill this vector with otherwise valid
candidates (other checks like "is it used?" still apply in this
context), and then perform the conflict check upon the already filled
vector.

Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com>

0 files changed, 0 insertions, 0 deletions