public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "robert at bedrocksystems dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/112353] New: asan-enabled, aarch64-gcc cross-compiled elf executables fail ro run in qemu-user on x86 Date: Thu, 02 Nov 2023 17:07:38 +0000 [thread overview] Message-ID: <bug-112353-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112353 Bug ID: 112353 Summary: asan-enabled, aarch64-gcc cross-compiled elf executables fail ro run in qemu-user on x86 Product: gcc Version: 12.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: robert at bedrocksystems dot com 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: --- On Ubuntu 23.04 x86_64, an aarch64 cross-compiled elf executable with Address Sanitizer (asan) enabled, fails with the run-time error: ``` AddressSanitizer: CHECK failed: asan_poisoning.cpp:38 "((AddrIsInMem(addr))) != (0)" (0x0, 0x0) (tid=1909) <empty stack> ``` This might be related to qemu and not gcc, but it reproduced also with gcc 13.2.0, but not with gcc 11.4.0. Versions used: ``` $ aarch64-linux-gnu-g++ --version aarch64-linux-gnu-g++ (Ubuntu 12.3.0-1ubuntu1~23.04) 12.3.0 $ qemu-aarch64-static -version qemu-aarch64 version 7.2.0 (Debian 1:7.2+dfsg-5ubuntu2.3) ``` Steps to reproduce: ``` $ echo "int main() {return 1;}" > /tmp/poc.cpp $ aarch64-linux-gnu-g++ -fsanitize=address /tmp/poc.cpp -o /tmp/poc $ qemu-aarch64-static /tmp/poc ## this takes a while AddressSanitizer: CHECK failed: asan_poisoning.cpp:38 "((AddrIsInMem(addr))) != (0)" (0x0, 0x0) (tid=2220) <empty stack> ```
next reply other threads:[~2023-11-02 17:07 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-02 17:07 robert at bedrocksystems dot com [this message] 2023-11-02 17:09 ` [Bug sanitizer/112353] " pinskia at gcc dot gnu.org 2023-11-21 23:26 ` pinskia at gcc dot gnu.org 2023-11-24 9:30 ` robert at bedrocksystems dot com
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=bug-112353-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).