--- Comment #5 from levharout at gmail dot com 2006-02-14 14:08 ---
(In reply to comment #4)
> So this is a purify bug as valgrind says the memory is still reachable which
> is
> correct because it is a thread specific location for the main thread. Closing
> as invalid.
Hello, I tried
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-01-19 17:53 ---
So this is a purify bug as valgrind says the memory is still reachable which is
correct because it is a thread specific location for the main thread. Closing
as invalid.
--
pinskia at gcc dot gnu dot org changed
--- Comment #3 from loizeaux1 at hotmail dot com 2006-01-19 17:30 ---
Here's the results I got after following the directions on the website you gave
me (I realize this may be moot since you pointed out that it is a false
positive, but I'll just do this for completeness' sake):
> cat te
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-01-18 21:30 ---
Also looking at the code:
void* v = std::malloc(sizeof(__cxa_eh_globals));
if (v == 0 || __gthread_setspecific(init._M_key, v) != 0)
std::terminate();
This is a false postive as we do
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-01-18 21:26 ---
Can you first read:
http://gcc.gnu.org/onlinedocs/libstdc++/debug.html#mem
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25849
