public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "m at matthewlai dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58038] std::this_thread::sleep_until can cause inifinite sleep
Date: Thu, 26 Mar 2015 20:27:00 -0000 [thread overview]
Message-ID: <bug-58038-4-ooentUZdzc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58038-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58038
--- Comment #13 from Matthew Lai <m at matthewlai dot ca> ---
(In reply to Jonathan Wakely from comment #11)
> (In reply to Matthew Lai from comment #8)
> > Here is another case where this bug caused a hard-to-find problem -
> > http://stackoverflow.com/questions/17574287/boostthread-attributes-setting-
> > call-stack-size
> >
> > (last comment)
>
> That seems to be about Boost.Thread so nothing to do with us.
Yeah that's in Boost, but it's the exact same bug in Boost. I linked it just to
show the kind of problem this can cause.
And thanks for the fix!
next prev parent reply other threads:[~2015-03-26 20:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 13:27 [Bug libstdc++/58038] New: " mario.bielert@tu-dresden.de
2013-07-31 14:02 ` [Bug libstdc++/58038] " redi at gcc dot gnu.org
2013-07-31 14:17 ` redi at gcc dot gnu.org
2013-07-31 14:35 ` redi at gcc dot gnu.org
2013-07-31 14:37 ` paolo.carlini at oracle dot com
2013-11-18 11:24 ` mario.bielert@tu-dresden.de
2013-11-18 11:42 ` redi at gcc dot gnu.org
2014-02-28 7:38 ` m at matthewlai dot ca
2014-05-14 20:37 ` m at matthewlai dot ca
2014-09-16 4:11 ` dan at stahlke dot org
2014-09-16 8:17 ` redi at gcc dot gnu.org
2015-03-26 20:06 ` redi at gcc dot gnu.org
2015-03-26 20:09 ` redi at gcc dot gnu.org
2015-03-26 20:09 ` redi at gcc dot gnu.org
2015-03-26 20:27 ` m at matthewlai dot ca [this message]
2015-04-11 11:47 ` redi at gcc dot gnu.org
2015-04-11 11:56 ` 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-58038-4-ooentUZdzc@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).