public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109548] Detect c_str() dangling problems Date: Wed, 19 Apr 2023 09:45:39 +0000 [thread overview] Message-ID: <bug-109548-4-jrXPYPxkYk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109548-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109548 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmalcolm at gcc dot gnu.org, | |rguenth at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- David possibly has inputs on how this should be done so the analyzer can do this kind of diagnostic. Generally I'd say we want sth like T * __attribute__ ((return_lifetime(1))) foo (U *p, ...); where we specify the lifetime of the returned referenced object to be the same as a referenced object in the argument list? So yes, the [[gnu::lifetime(this)]] attribution would maybe do that but can the attribute refer to another explicitely named argument as well? Btw, is there an API to std::move the (possibly) allocated string out of the std::string and make it available as C string pointer?
next prev parent reply other threads:[~2023-04-19 9:45 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-18 23:19 [Bug c++/109548] New: " paul.f.fee at gmail dot com 2023-04-18 23:34 ` [Bug c++/109548] " pinskia at gcc dot gnu.org 2023-04-19 8:59 ` redi at gcc dot gnu.org 2023-04-19 9:45 ` rguenth at gcc dot gnu.org [this message] 2023-04-19 12:38 ` redi 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-109548-4-jrXPYPxkYk@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).