public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/112314] Missing index assertions in basic_string_view Date: Tue, 31 Oct 2023 15:28:53 +0000 [thread overview] Message-ID: <bug-112314-4-BQHXXTrsYY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112314-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112314 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2023-10-31 Severity|normal |enhancement --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- For the first problem: --- a/libstdc++-v3/include/std/string_view +++ b/libstdc++-v3/include/std/string_view @@ -301,7 +301,10 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION constexpr void remove_suffix(size_type __n) noexcept - { this->_M_len -= __n; } + { + __glibcxx_assert(this->_M_len >= __n); + this->_M_len -= __n; + } constexpr void swap(basic_string_view& __sv) noexcept For the second one, I did start work on a patch that attempts to verify that the provided length is not more than __builtin_object_size. I can't remember why I stopped working on that. There's no way to make that check 100% reliable, because __builtin_object_size depends on optimizations and whether the compiler can see enough data.
next prev parent reply other threads:[~2023-10-31 15:28 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-31 12:05 [Bug libstdc++/112314] New: " jdapena at igalia dot com 2023-10-31 15:28 ` redi at gcc dot gnu.org [this message] 2023-11-02 8:47 ` [Bug libstdc++/112314] " jdapena at igalia dot com 2023-11-02 14:54 ` cvs-commit at gcc dot gnu.org 2023-11-02 16:06 ` redi at gcc dot gnu.org 2023-11-02 16:19 ` jdapena at igalia dot com 2023-11-02 17:37 ` redi at gcc dot gnu.org 2023-11-02 17:40 ` redi at gcc dot gnu.org 2023-11-08 13:18 ` cvs-commit at gcc dot gnu.org 2023-12-06 16:35 ` cvs-commit at gcc dot gnu.org 2023-12-06 21:01 ` cvs-commit 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-112314-4-BQHXXTrsYY@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: linkBe 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).