[Bug libstdc++/42734] New: trivial use of std::thread fails with "pure virtual method called"

[Bug libstdc++/42734] New: trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

---------- code ----------------

#include <cstdio>
#include <thread>

using namespace std;

void f()
{
    fputs("f()\n", stderr);
}

int main()
{
    fputs("before new thread\n", stderr);
    thread t(f);
    fputs("after new thread\n", stderr);
    t.join();
    fputs("after join\n", stderr);

    return 0;
}

---------- system information ----------------

uname -a:
Linux nuty 2.6.33-rc2-zen1-zen-nuty-07221-g526ecd7 #4 ZEN PREEMPT Sun Jan 10
23:33:42 CET 2010 i686 Intel(R) Pentium(R) M processor 1.40GHz GenuineIntel
GNU/Linux

gcc --version:
gcc (GCC) 4.4.2 20091208 (prerelease)
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

---------- complier arguments ----------------

$ g++ -std=c++0x -pthread thread.cc -o thread

---------- output ----------------

before new thread
after new thread
pure virtual method called
terminate called without an active exception

---------- gdb run ----------------

(gdb) r
Starting program: /tmp/thread 
[Thread debugging using libthread_db enabled]
before new thread
[New Thread 0xb7d30b70 (LWP 5676)]
after new thread
pure virtual method called
terminate called without an active exception

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb7d30b70 (LWP 5676)]
0xb7fe1424 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7fe1424 in __kernel_vsyscall ()
#1  0xb7d5c571 in raise () from /lib/libc.so.6
#2  0xb7d5dd72 in abort () from /lib/libc.so.6
#3  0xb7f9352f in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/libstdc++.so.6
#4  0xb7f90eb5 in __cxxabiv1::__terminate(void (*)()) () from
/usr/lib/libstdc++.so.6
#5  0xb7f90ef2 in std::terminate() () from /usr/lib/libstdc++.so.6
#6  0xb7f92155 in __cxa_pure_virtual () from /usr/lib/libstdc++.so.6
#7  0xb7f89c16 in execute_native_thread_routine () from /usr/lib/libstdc++.so.6
#8  0xb7e7f8ac in start_thread () from /lib/libpthread.so.0
#9  0xb7e0001e in clone () from /lib/libc.so.6
(gdb) info threads
* 2 Thread 0xb7d30b70 (LWP 5676)  0xb7fe1424 in __kernel_vsyscall ()
  1 Thread 0xb7d316d0 (LWP 5673)  0xb7fe1424 in __kernel_vsyscall ()
(gdb) thread 1
[Switching to thread 1 (Thread 0xb7d316d0 (LWP 5673))]#0  0xb7fe1424 in
__kernel_vsyscall ()
(gdb) bt
#0  0xb7fe1424 in __kernel_vsyscall ()
#1  0xb7e80a3d in pthread_join () from /lib/libpthread.so.0
#2  0xb7f89b22 in std::thread::join() () from /usr/lib/libstdc++.so.6
#3  0x08048b30 in main () at thread.cc:16
(gdb)


-- 
           Summary: trivial use of std::thread fails with "pure virtual
                    method called"
           Product: gcc
           Version: 4.4.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: phil at nwl dot cc


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #1 from phil at nwl dot cc  2010-01-13 20:22 -------
Created an attachment (id=19580)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19580&action=view)
preprocessor output generated by -save-temps


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #2 from phil at nwl dot cc  2010-01-13 20:23 -------
Created an attachment (id=19581)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19581&action=view)
assembly output generated by -save-temps


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #3 from phil at nwl dot cc  2010-01-13 20:23 -------
Created an attachment (id=19582)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19582&action=view)
output when running the test program through valgrind


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #4 from paolo dot carlini at oracle dot com  2010-01-13 20:40 -------
I cannot reproduce the problem in current 4_4-branch and mainline. Jon does it
make any sense to you? 


-- 

paolo dot carlini at oracle dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jwakely dot gcc at gmail dot
                   |                            |com
      Known to work|                            |4.4.3 4.5.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[redi at gcc dot gnu dot org]

------- Comment #5 from redi at gcc dot gnu dot org  2010-01-13 21:33 -------
It would be a lot easier to view the attachments if they were labelled as text
files, but no, I can't see how this can happen.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[redi at gcc dot gnu dot org]

------- Comment #6 from redi at gcc dot gnu dot org  2010-01-13 21:37 -------
does the g++ binary, gcc (GCC) 4.4.2 20091208 (prerelease), match the shared
library, /usr/lib/libstdc++.so.6.0.13?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #7 from phil at nwl dot cc  2010-01-13 22:34 -------
(In reply to comment #6)
> does the g++ binary, gcc (GCC) 4.4.2 20091208 (prerelease), match the shared
> library, /usr/lib/libstdc++.so.6.0.13?
>

Yes, it does. The executable is linked against libstdc++.so.6, being a symlink
to libstdc++.so.6.0.13.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #8 from phil at nwl dot cc  2010-01-13 22:37 -------
(In reply to comment #4)
> I cannot reproduce the problem in current 4_4-branch and mainline. Jon does it
> make any sense to you? 
> 

It seems like this bug exists only on x86 machines, but I don't have any x86_64
machine with gcc-4.4 available to verify that.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #9 from paolo dot carlini at oracle dot com  2010-01-13 22:39 -------
But note that I can't reproduce it on x86_64 and -m32


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #10 from paolo dot carlini at oracle dot com  2010-01-13 22:40 -------
-m64 (the default) is also fine, of course.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #11 from phil at nwl dot cc  2010-01-13 22:52 -------
(In reply to comment #9)
> But note that I can't reproduce it on x86_64 and -m32
> 

Was told that, too. So what can I do to support you? What additional
information should I provide? I could probably setup some shell access to the
faulty machine (have to setup some dyndns first, though).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #12 from paolo dot carlini at oracle dot com  2010-01-13 23:09 -------
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.
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.




-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[redi at gcc dot gnu dot org]

------- Comment #13 from redi at gcc dot gnu dot org  2010-01-13 23:34 -------
(In reply to comment #9)
> But note that I can't reproduce it on x86_64 and -m32

It is possible to build a non-multilib 32-bit-only compiler on x86_64 - HJ gave
Benjamin the right configure commands recently.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- 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

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #15 from paolo dot carlini at oracle dot com  2010-01-14 01:58 -------
(In reply to comment #14)
> Believe it or not, "nuty" is actually the hostname of the system in question.
> ;)
> 
> The distribution is Arch Linux.

Believe it or not, I don't know Arch Linux either ;)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

-- 

paolo dot carlini at oracle dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #16 from phil at nwl dot cc  2010-01-15 01:49 -------
(In reply to comment #14)
> I'll give the testsuite a try, but this will take some time (svn checkout is
> still running).
> 

Oh boy, here it comes. I hope I've done the right thing, as there is little
documentation about how to run the testsuite ('make check-g++' seems not to
work for testing out-of-tree-binaries).

What I did:
- checkout svn://gcc.gnu.org/svn/gcc/trunk
- cd $checkout/gcc && runtest --tool g++ --srcdir ./testsuite
(output files g++.{log,sum} follow as attachments)

I'll appreciate instructions if this was all useless. :)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #17 from phil at nwl dot cc  2010-01-15 01:55 -------
(In reply to comment #16)
> (output files g++.{log,sum} follow as attachments)

Mkay, bugzilla doesn't like the big logs. Meanwhile, take these:
- http://nwl.cc/~n0-1/g++.log
- http://nwl.cc/~n0-1/g++.sum


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #18 from paolo dot carlini at oracle dot com  2010-01-15 02:00 -------
Just build everything with default configure options, then go inside the
libstdc++-v3 *build* dir and type 'make check'.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #19 from paolo dot carlini at oracle dot com  2010-01-15 02:02 -------
(we are not particularly interested in the g++ testresults, that this the
results for the C++ front-end proper, we are interested in the library results)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #20 from paolo dot carlini at oracle dot com  2010-01-15 02:05 -------
Normally should look, for your i686 target, like the final part of this:

  http://gcc.gnu.org/ml/gcc-testresults/2010-01/msg01263.html

(please disregard the 23_containers failures, it's a temporary problem, will go
away soon)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #21 from phil at nwl dot cc  2010-01-15 22:07 -------
(In reply to comment #18)
> Just build everything with default configure options, then go inside the
> libstdc++-v3 *build* dir and type 'make check'.

Ah, hmm. Well, having to compile everything in order to run the tests using an
external compiler is a bit of a bummer, isn't it?

Compiling will take some time on this X40, so please be patient. :)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #22 from paolo dot carlini at oracle dot com  2010-01-15 22:15 -------
(In reply to comment #21)
> (In reply to comment #18)
> > Just build everything with default configure options, then go inside the
> > libstdc++-v3 *build* dir and type 'make check'.
> 
> Ah, hmm. Well, having to compile everything in order to run the tests using an
> external compiler is a bit of a bummer, isn't it?

Maybe there is a communication problem here: I meant, *the whole GCC*,
normally, with no special options, to keep things simple. If you want, you can
exclude java, which normally takes a while, and fortran, and objective c, the
languages you don't need in other terms: just pass --enable-languages=c++ and
nothing else.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #23 from phil at nwl dot cc  2010-01-15 22:32 -------
(In reply to comment #22)
> (In reply to comment #21)
> > (In reply to comment #18)
> > > Just build everything with default configure options, then go inside the
> > > libstdc++-v3 *build* dir and type 'make check'.
> > 
> > Ah, hmm. Well, having to compile everything in order to run the tests using an
> > external compiler is a bit of a bummer, isn't it?
> 
> Maybe there is a communication problem here: I meant, *the whole GCC*,

Yes, it seems so.

> normally, with no special options, to keep things simple. If you want, you can
> exclude java, which normally takes a while, and fortran, and objective c, the
> languages you don't need in other terms: just pass --enable-languages=c++ and
> nothing else.

What we want to do is to run the libstdc++ testsuite with my
distribution-provided g++, in order to see whether it's generally broken or
not, right?

And what I'm criticising here is that I have to compile *anything* of the
gcc-sources in order to run the testsuite. I see no sense in building any
binaries at all, since I already have all binaries (executables as well as
libraries) in order to run the tests?!


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #24 from paolo dot carlini at oracle dot com  2010-01-15 23:07 -------
(In reply to comment #23)
> What we want to do is to run the libstdc++ testsuite with my
> distribution-provided g++, in order to see whether it's generally broken or
> not, right?

Wrong. You can't use one compiler (older, by the way), with a newer libstdc++.

> And what I'm criticising here is that I have to compile *anything* of the
> gcc-sources in order to run the testsuite. I see no sense in building any
> binaries at all, since I already have all binaries (executables as well as
> libraries) in order to run the tests?!

You don't, you *need* a complete new GCC.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #25 from phil at nwl dot cc  2010-01-15 23:49 -------
(In reply to comment #24)
> (In reply to comment #23)
> > What we want to do is to run the libstdc++ testsuite with my
> > distribution-provided g++, in order to see whether it's generally broken or
> > not, right?
> 
> Wrong. You can't use one compiler (older, by the way), with a newer libstdc++.
> 
> > And what I'm criticising here is that I have to compile *anything* of the
> > gcc-sources in order to run the testsuite. I see no sense in building any
> > binaries at all, since I already have all binaries (executables as well as
> > libraries) in order to run the tests?!
> 
> You don't, you *need* a complete new GCC.

Ok. So what's the point in doing this, then?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #26 from paolo dot carlini at oracle dot com  2010-01-16 00:05 -------
Hey, I'm telling you the way we all library maintainers (like me) and users
check the library: they all fetch everything (either mainline or 4_4-branch, or
whatever) via svn, make, make check. Now you want to do something else, you
want to check the compiler + library you have already installed, but your
obviously missing the testsuite, because you didn't build it yourself. Now, you
are on your own, because I have no idea how and where to fetch only the
testsuite of the specific GCC you are running on the specific Linux you are
running, and then adjust everything to run it with your already installed
compiler, this is not the normal way we do those tests.

To repeat, the point was checking that your Linux and your hardware are sane,
because I told you already that we know **for sure** that on current (and no so
current) machines and Ubuntu, OpenSUSE, Fedora, whatever, that snippet works
perfectly fine and *much* more than it, a whole testsuite.

So, it's up to you, I'll keep this open: if over the nest month or so you
provide the testresults you get for either your specific GCC, current
4_4-branch, or current mainline on your OS + hardware, we can hope to make
progress on your issue, otherwise nobody will commit suicide, and the issue
will be simply closed for lack of meaningful feedback from submitter.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[phil at nwl dot cc]

------- Comment #27 from phil at nwl dot cc  2010-01-16 01:08 -------
(In reply to comment #26)
> Hey, I'm telling you the way we all library maintainers (like me) and users
> check the library: they all fetch everything (either mainline or 4_4-branch, or
> whatever) via svn, make, make check. Now you want to do something else, you
> want to check the compiler + library you have already installed, but your
> obviously missing the testsuite, because you didn't build it yourself. Now, you
> are on your own, because I have no idea how and where to fetch only the
> testsuite of the specific GCC you are running on the specific Linux you are
> running, and then adjust everything to run it with your already installed
> compiler, this is not the normal way we do those tests.
> 
> To repeat, the point was checking that your Linux and your hardware are sane,
> because I told you already that we know **for sure** that on current (and no so
> current) machines and Ubuntu, OpenSUSE, Fedora, whatever, that snippet works
> perfectly fine and *much* more than it, a whole testsuite.
> 
> So, it's up to you, I'll keep this open: if over the nest month or so you
> provide the testresults you get for either your specific GCC, current
> 4_4-branch, or current mainline on your OS + hardware, we can hope to make
> progress on your issue, otherwise nobody will commit suicide, and the issue
> will be simply closed for lack of meaningful feedback from submitter.

It's ok man, no offense here. I really didn't want to stomp on any feet.

All I'm trying to do is to figure out why I'm having this problem and how to
fix it. Abusing this bug tracker for a little conversation was a pleasure to
me, getting you upset wasn't my intention. My apologies for that.

So I will just do as you say and try to fix my distribution (or bug it's
maintainers) instead of getting into your way. Anyway, thanks a lot for your
help so far.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734

[Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"

[paolo dot carlini at oracle dot com]

------- Comment #28 from paolo dot carlini at oracle dot com  2010-01-16 10:10 -------
Feedback not forthcoming.


-- 

paolo dot carlini at oracle dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42734