public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "phil at nwl dot cc" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"
Date: Thu, 14 Jan 2010 01:14:00 -0000 [thread overview]
Message-ID: <20100114011355.6167.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42734-18664@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from phil at nwl dot cc 2010-01-14 01:13 -------
(In reply to comment #12)
> Before anything else, you should make sure your system is otherwise sane, I
> don't know "Linux nuty" and I have no idea if it's affected by specific issues.
Believe it or not, "nuty" is actually the hostname of the system in question.
;)
The distribution is Arch Linux.
> Thus, first, I would suggest you to run the testsuite, which among many other
> things includes lots of tests of the <thread> facilities, which should all pass
> on x86 and x86_64 linux, see the gcc-testresults mailing list. If <thread> were
> broken as seriously as you are reporting on the main Linux distros, we would
> definitely know by now, because the testsuite tests *much* more than your
> snippet.
I'll give the testsuite a try, but this will take some time (svn checkout is
still running).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734
next prev parent reply other threads:[~2010-01-14 1:14 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 20:21 [Bug libstdc++/42734] New: " phil at nwl dot cc
2010-01-13 20:22 ` [Bug libstdc++/42734] " phil at nwl dot cc
2010-01-13 20:23 ` phil at nwl dot cc
2010-01-13 20:24 ` phil at nwl dot cc
2010-01-13 20:41 ` paolo dot carlini at oracle dot com
2010-01-13 21:33 ` redi at gcc dot gnu dot org
2010-01-13 21:37 ` redi at gcc dot gnu dot org
2010-01-13 22:34 ` phil at nwl dot cc
2010-01-13 22:37 ` phil at nwl dot cc
2010-01-13 22:40 ` paolo dot carlini at oracle dot com
2010-01-13 22:40 ` paolo dot carlini at oracle dot com
2010-01-13 22:53 ` phil at nwl dot cc
2010-01-13 23:10 ` paolo dot carlini at oracle dot com
2010-01-13 23:34 ` redi at gcc dot gnu dot org
2010-01-14 1:14 ` phil at nwl dot cc [this message]
2010-01-14 1:59 ` paolo dot carlini at oracle dot com
2010-01-14 21:36 ` paolo dot carlini at oracle dot com
2010-01-15 1:49 ` phil at nwl dot cc
2010-01-15 1:55 ` phil at nwl dot cc
2010-01-15 2:00 ` paolo dot carlini at oracle dot com
2010-01-15 2:02 ` paolo dot carlini at oracle dot com
2010-01-15 2:05 ` paolo dot carlini at oracle dot com
2010-01-15 22:07 ` phil at nwl dot cc
2010-01-15 22:15 ` paolo dot carlini at oracle dot com
2010-01-15 22:32 ` phil at nwl dot cc
2010-01-15 23:07 ` paolo dot carlini at oracle dot com
2010-01-15 23:49 ` phil at nwl dot cc
2010-01-16 0:05 ` paolo dot carlini at oracle dot com
2010-01-16 1:08 ` phil at nwl dot cc
2010-01-16 10:10 ` paolo dot carlini at oracle dot com
[not found] <bug-42734-4@http.gcc.gnu.org/bugzilla/>
2010-10-15 18:46 ` nacitar at gmail dot com
2010-10-15 18:49 ` pinskia at gcc dot gnu.org
2010-10-15 19:28 ` redi at gcc dot gnu.org
2010-10-15 19:38 ` redi at gcc dot gnu.org
2010-10-15 19:45 ` redi at gcc dot gnu.org
2010-10-15 19:47 ` nacitar at gmail dot com
2010-10-15 20:07 ` redi at gcc dot gnu.org
2010-10-15 23:42 ` paolo.carlini at oracle dot com
2010-10-16 13:32 ` redi at gcc dot gnu.org
2010-10-16 15:54 ` redi at gcc dot gnu.org
2010-10-17 9:57 ` paolo.carlini at oracle dot com
2014-07-18 5:43 ` damien.buhl at lecbna dot org
2014-12-03 18:40 ` fenixk19 at mail dot ru
2014-12-04 12:52 ` fenixk19 at mail dot ru
2014-12-04 12:55 ` damien.buhl at lecbna dot org
2014-12-04 19:28 ` fenixk19 at mail dot ru
2014-12-05 0:26 ` damien.buhl at lecbna dot org
2014-12-08 15:54 ` damien.buhl at lecbna dot org
2014-12-08 21:05 ` fenixk19 at mail dot ru
2015-10-05 10:18 ` 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=20100114011355.6167.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: 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).