public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rachel at rachelmant dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/94849] Improper parameter validation in libsanitizer for fopen64
Date: Wed, 29 Apr 2020 15:52:34 +0000	[thread overview]
Message-ID: <bug-94849-4-lujbFOErEX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94849-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Rachel Mant <rachel at rachelmant dot com> ---
Continuing to think on this a bit, and.. if it is undefined behaviour as you
say, then granted this is not a bug on ASAN/TSAN.. but it is still a bug as
UBSAN does and says nothing when faced with this even though it clearly should
terminate the program for invoking UB, with a suitable diagnostic.

  parent reply	other threads:[~2020-04-29 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 14:22 [Bug sanitizer/94849] New: " rachel at rachelmant dot com
2020-04-29 14:28 ` [Bug sanitizer/94849] " marxin at gcc dot gnu.org
2020-04-29 14:30 ` jakub at gcc dot gnu.org
2020-04-29 14:33 ` marxin at gcc dot gnu.org
2020-04-29 14:38 ` rachel at rachelmant dot com
2020-04-29 14:53 ` jakub at gcc dot gnu.org
2020-04-29 15:03 ` rachel at rachelmant dot com
2020-04-29 15:52 ` rachel at rachelmant dot com [this message]
2020-04-30 19:03 ` msebor at gcc dot gnu.org
2020-05-04 18:12 ` 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-94849-4-lujbFOErEX@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).