public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nrk at disroot dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/110676] New: builtin optimization prevents ASan from detecting OOB reads
Date: Sat, 15 Jul 2023 18:28:05 +0000	[thread overview]
Message-ID: <bug-110676-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110676
           Summary: builtin optimization prevents ASan from detecting OOB
                    reads
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nrk at disroot dot org
                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: ---

Minimal reproducible code-snippet:

#include <string.h>

int main(void)
{
        char s[1] = "A";
        return strlen(s);
}

Compile command: gcc -O0 -g3 -fsanitize=address,undefined
Expected behavior: ASan should catch the OOB access.
Reality: It gets optimized out and returns 0 always.
Note: adding `-fno-builtin` allows ASan to be effective.

             reply	other threads:[~2023-07-15 18:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15 18:28 nrk at disroot dot org [this message]
2023-07-15 18:32 ` [Bug sanitizer/110676] strlen of array[1] should not be optimized to 1 if using ASAN pinskia at gcc dot gnu.org
2023-07-15 18:35 ` [Bug sanitizer/110676] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-07-15 18:35 ` nrk at disroot dot org
2024-02-05 20:23 ` [Bug sanitizer/110676] [11/12/13/14 Regression] strlen of array[1] should not be optimized to 0 " jakub at gcc dot gnu.org
2024-02-05 20:47 ` jakub at gcc dot gnu.org
2024-02-06 12:00 ` cvs-commit at gcc dot gnu.org
2024-02-06 12:01 ` [Bug sanitizer/110676] [11/12/13 " jakub at gcc dot gnu.org
2024-05-13 11:33 ` rguenth 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-110676-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: 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).