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/105405] missed buffer-overflow in -O0
Date: Wed, 27 Apr 2022 11:04:25 +0000	[thread overview]
Message-ID: <bug-105405-4-Yj28rOwu44@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105405-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think that is just misunderstanding on how ASan works and what it can
protect. It adds red zone around vars, so that access right after end of var or
before start of var is reported. But the red zone is quite small and needs to
be if we don't want to blow the whole stack, so if the overflow is farther away
and you are unlucky enough to reaching another var, it won't be diagnosed.
-fsanitize=undefined

  parent reply	other threads:[~2022-04-27 11:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 10:02 [Bug sanitizer/105405] New: " shaohua.li at inf dot ethz.ch
2022-04-27 10:07 ` [Bug sanitizer/105405] " marxin at gcc dot gnu.org
2022-04-27 10:25 ` shaohua.li at inf dot ethz.ch
2022-04-27 11:04 ` jakub at gcc dot gnu.org [this message]
2022-04-28  8:54 ` shaohua.li at inf dot ethz.ch
2022-04-28  9:04 ` jakub at gcc dot gnu.org
2022-04-28  9:11 ` 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-105405-4-Yj28rOwu44@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).