[Bug sanitizer/108021] sanitizer used with qemu

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108021

--- Comment #1 from Andrew Pinski  ---
https://gcc.gnu.org/pipermail/gcc-patches/2020-February/540024.html

[Bug sanitizer/108021] sanitizer used with qemu

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108021

--- Comment #2 from Andrew Pinski  ---
I have not tried the trunk with these patches though. The patches I did were
for GCC 10.

[Bug sanitizer/108021] sanitizer used with qemu

[laurent.alfonsi at linaro dot org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108021

laurent.alfonsi at linaro dot org  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from laurent.alfonsi at linaro dot org  ---
I have tested with future merged branch of qemu 
  https://gitlab.com/stsquad/qemu/-/commits/review/linux-user-vma-v2

and it fail properly 
  $ qemu-aarch64  -L sysroot-with-libasan-from-master-branch  ./a.out
  AddressSanitizer: CHECK failed: asan_poisoning.cpp:38 "((AddrIsInMem(addr)))
!= (0)" (0x0, 0x0) (tid=16754)


The RAM memory doesn't grow continuously anymore.

>From my pov, it is fair. This issue that will be fixed when merging the qemu
branch.