[Bug sanitizer/108021] New: sanitizer used with qemu

[Bug sanitizer/108021] New: sanitizer used with qemu

[laurent.alfonsi at linaro dot org]

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

            Bug ID: 108021
           Summary: sanitizer used with qemu
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: laurent.alfonsi at linaro dot org
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
  Target Milestone: ---

Hi,

I m running gcc testsuite with qemu, and I am facing an issue in sanitizer.

Before (12.x), the asan was incompatible with ptrace.
   $ cat emtpy.c
    int main(void) { return 0; }

   $ aarch64-linux-gnu-gcc emtpy.c -fsanitize=address

   $ qemu-aarch64 -L ./sysroot-with-libasan-from-release ./a.out
    ==135765==LeakSanitizer has encountered a fatal error.
    ==135765==HINT: For debugging, try setting environment variable
LSAN_OPTIONS=verbosity=1:log_threads=1
    ==135765==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc)
      # fiishes quickly : return status=1


Now (13.x), 
   $ qemu-aarch64 -L ./sysroot-with-libasan-from-master-branch ./a.out
      # RAM memory grows exponentially without message

It happens of course on most asan-dg.exp tests

Either, it has been changed and not incompatible anymore with ptrace, or the
error message was removed by error.

It happens of course on most asan-dg.exp tests. 
Is this supposed to work now ?

[Bug sanitizer/108021] sanitizer used with qemu

[pinskia at gcc dot gnu.org]

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

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

[Bug sanitizer/108021] sanitizer used with qemu

[pinskia at gcc dot gnu.org]

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
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]

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

laurent.alfonsi at linaro dot org <laurent.alfonsi at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from laurent.alfonsi at linaro dot org <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)
    <empty stack>

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.