public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/79341] Many Asan tests fail on s390
Date: Sat, 30 Mar 2024 17:40:45 +0000 [thread overview]
Message-ID: <bug-79341-4-aDsS8aKDqg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-79341-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79341
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #75 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Dominik Vogt from comment #25)
> Looks better, but now we get this quite often:
>
> --
> ==23722==ERROR: Your kernel seems to be vulnerable to CVE-2016-2143. Using
> ASa\
> n,
> MSan, TSan, DFSan or LSan with such kernel can and will crash your
> machine, or worse.
> --
>
> I'll try to figure out what kernel version we need.
Why does this error message mention all of those sanitizers, when GCC only
supports some of them?
next parent reply other threads:[~2024-03-30 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-79341-4@http.gcc.gnu.org/bugzilla/>
2024-03-30 17:40 ` egallager at gcc dot gnu.org [this message]
2024-04-03 11:25 ` iii at linux dot ibm.com
2024-04-04 13:09 ` iii at linux dot ibm.com
2024-05-04 7:31 ` egallager at gcc dot gnu.org
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-79341-4-aDsS8aKDqg@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: 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).