public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/45133] [c++0x] std::future will crash with NULL deref if get() is called twice Date: Fri, 30 Jul 2010 14:30:00 -0000 [thread overview] Message-ID: <20100730143036.9068.qmail@sourceware.org> (raw) In-Reply-To: <bug-45133-6477@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from redi at gcc dot gnu dot org 2010-07-30 14:30 ------- (In reply to comment #0) > > I would assume the result of doing a get() when !valid() is undefined, No need to assume, it's stated explicitly in the FCD. > so > throwing an exception when someone does this would be conforming, and a lot > more obvious and friendly. If for some reason this couldn't work, even just an > assertion fail would be more informative than a NULL pointer deref. Confirming, as an enhancement request. I'm travelling until Tuesday so won't look in detail right now, but IIRC there are possible race conditions so it's not necessarily as simple as just checking for a NULL pointer. -- redi at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |redi at gcc dot gnu dot org |dot org | Severity|normal |enhancement Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2010-07-30 14:30:35 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45133
next prev parent reply other threads:[~2010-07-30 14:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-29 15:53 [Bug libstdc++/45133] New: " lloyd at randombit dot net 2010-07-29 17:35 ` [Bug libstdc++/45133] " paolo dot carlini at oracle dot com 2010-07-30 14:30 ` redi at gcc dot gnu dot org [this message] 2010-07-30 14:39 ` redi at gcc dot gnu dot org 2010-08-06 15:36 ` redi at gcc dot gnu dot org [not found] <bug-45133-4@http.gcc.gnu.org/bugzilla/> 2010-12-03 15:39 ` redi at gcc dot gnu.org 2010-12-14 23:27 ` redi at gcc dot gnu.org 2010-12-14 23:33 ` 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=20100730143036.9068.qmail@sourceware.org \ --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).