public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/107410] ASan failed to detect a  heap-buffer-overflow
Date: Wed, 26 Oct 2022 10:43:19 +0000	[thread overview]
Message-ID: <bug-107410-4-TdhsJz8f8m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107410-4@http.gcc.gnu.org/bugzilla/>

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Well, the test-case is very fragile and we tend to optimize out another UBSAN
stuff (c[i] = 2;). 

Please provide a test-case that addresses the buffer-overflow due does not
contain an UBSAN:

$ gcc-12 broken.c -fsanitize=undefined -w && ./a.out
broken.c:15:6: runtime error: index 19 out of bounds for type 'char [2]'
broken.c:15:10: runtime error: store to address 0x7fffffffd5bd with
insufficient space for an object of type 'char'
0x7fffffffd5bd: note: pointer points here
 d5 ff ff ff 7f 00 00  00 20 01 00 00 00 00 00  e8 d6 ff ff ff 7f 00 00  01 00
00 00 00 00 00 00  b0
             ^ 
broken.c:17:8: runtime error: index 19 out of bounds for type 'char [2]'
broken.c:17:8: runtime error: load of address 0x7fffffffd5bd with insufficient
space for an object of type 'char'
0x7fffffffd5bd: note: pointer points here
 d5 ff ff ff 02 00 00  00 20 01 00 00 00 00 00  e8 d6 ff ff ff 7f 00 00  01 00
00 00 00 00 00 00  b0
             ^

      parent reply	other threads:[~2022-10-26 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26  9:07 [Bug sanitizer/107410] New: " shaohua.li at inf dot ethz.ch
2022-10-26  9:13 ` [Bug sanitizer/107410] " shaohua.li at inf dot ethz.ch
2022-10-26 10:43 ` marxin at gcc dot gnu.org [this message]

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-107410-4-TdhsJz8f8m@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).