public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Deepthi H <deepadeepthi98@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Sanitizer CHECK failed: sanitizer_allocator_primary64.h:133
Date: Fri, 09 Feb 2024 07:42:05 +0000	[thread overview]
Message-ID: <875xyyt76u.fsf@gentoo.org> (raw)
In-Reply-To: <CAMtd7J6T9HicddjpyhMxWtL0pbKPqrS_AtyTDLY4=YMgAFckCg@mail.gmail.com>


Deepthi H via Gcc-help <gcc-help@gcc.gnu.org> writes:

> Hi all,
>
> I am facing the issue on enabling sanitizers for gcc on aarch64 linux.
> The issue was observed with the following command :-
> "aarch64-poky-linux-gcc -O1 -fsanitize=address -fno-omit-frame-pointer -o
> test test.c"
>
> *AddressSanitizer: CHECK failed: sanitizer_allocator_primary64.h:131
> "((kSpaceBeg)) == ((address_range.Init(TotalSpaceSize,
> PrimaryAllocatorName, kSpaceBeg)))" (0x600000000000, 0xfffffffffffffff4)
> (tid=389)    <empty stack>*
>
> I found a patch that fixes the sanitizer issue for arm64  on llvm :-
> ⚙D60243 [LSan][AArch64] Speed-up leak and address sanitizers on AArch64 for
> 48-bit VMA (llvm.org) <https://reviews.llvm.org/D60243#change-1yIlOwF0zl2Y>

That should've been synced into GCC ages ago. What version of GCC are
you using?

>
> I analyzed and tried to port the patch that fixes the issue for llvm. After
> backporting the LLVM patches to the GCC sources, I encountered several
> build errors, particularly related to the AddressSanitizer (ASan) and
> LeakSanitizer (LSan) libraries. I have fixed lsan and asan issues. However
> sanitizer_common is completely different in gcc than llvm.
> Can you please help me fix this issue on gcc sources or is than any other
> way to fix this issue.
>
> Thanks in advance,
> Deepthi


  reply	other threads:[~2024-02-09  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09  7:31 Deepthi H
2024-02-09  7:42 ` Sam James [this message]
2024-02-09  8:25   ` Deepthi H

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875xyyt76u.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=deepadeepthi98@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).