public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/106558] ASan failed to detect a global-buffer-overflow
Date: Wed, 10 Aug 2022 09:51:52 +0000	[thread overview]
Message-ID: <bug-106558-4-OvPH0k8z7Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106558-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Or perhaps could we ask the alias oracle in can_remove_asan_check
for the *base_checks case if base_addr lives in memory whether base_addr could
change in between the stmt in the vector and current stmt, with some low limit
on  how much we walk to find that out?

  parent reply	other threads:[~2022-08-10  9:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 12:05 [Bug sanitizer/106558] New: " shaohua.li at inf dot ethz.ch
2022-08-09  0:30 ` [Bug sanitizer/106558] " pinskia at gcc dot gnu.org
2022-08-09 12:30 ` marxin at gcc dot gnu.org
2022-08-10  9:20 ` jakub at gcc dot gnu.org
2022-08-10  9:35 ` jakub at gcc dot gnu.org
2022-08-10  9:49 ` tetra2005 at gmail dot com
2022-08-10  9:51 ` jakub at gcc dot gnu.org [this message]
2022-08-10 10:13 ` jakub at gcc dot gnu.org
2022-08-11 14:32 ` tetra2005 at gmail dot com
2022-08-11 15:01 ` jakub at gcc dot gnu.org
2022-08-15 11:03 ` ygribov at gcc dot gnu.org
2022-09-02  3:38 ` ygribov at gcc dot gnu.org
2022-09-02  3:38 ` ygribov at gcc dot gnu.org
2022-09-13 13:56 ` tetra2005 at gmail dot com
2022-11-07  9:14 ` shaohua.li at inf dot ethz.ch
2022-11-21  9:48 ` marxin at gcc dot gnu.org
2022-11-21  9:49 ` marxin at gcc dot gnu.org
2022-11-21 11:50 ` tetra2005 at gmail dot com
2022-11-22 12:21 ` marxin at gcc dot gnu.org
2022-11-28  9:49 ` cvs-commit at gcc dot gnu.org
2022-11-28  9:52 ` marxin at gcc dot gnu.org
2022-12-02 12:51 ` marxin 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-106558-4-OvPH0k8z7Q@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).