|
From: Kjartan M. <km...@br...> - 2006-01-20 12:48:24
|
Hi. I reported a bug wrt leaks in the new memory allocator in Glib and the comments in the bugreport ended like this: "to me it looks like valgrind needs better support for pthread_setspecific(3)." Can anyone take a look at the bugreport and tell me if I should file a bug against valgrind for this issue? Report his here: http://bugzilla.gnome.org/show_bug.cgi?id=324438 Cheers Kjartan |
|
From: Tom H. <to...@co...> - 2006-01-20 14:43:27
|
In message <1137761323.8800.5.camel@localhost.localdomain>
Kjartan Maraas <km...@br...> wrote:
> I reported a bug wrt leaks in the new memory allocator in Glib and the
> comments in the bugreport ended like this:
>
> "to me it looks like valgrind needs better support for
> pthread_setspecific(3)."
>
> Can anyone take a look at the bugreport and tell me if I should file a
> bug against valgrind for this issue?
>
> Report his here:
> http://bugzilla.gnome.org/show_bug.cgi?id=324438
You don't say what version of valgrind you're using, but no recent
version knows anything about any part of pthreads - it works at a
lower level than that.
Specifically, for thread specific data, it will simply see the system
fiddling with the LDT and/or GDT and take the appropriate actions.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Kjartan M. <km...@br...> - 2006-01-20 15:57:49
|
fre, 20,.01.2006 kl. 14.43 +0000, skrev Tom Hughes: > In message <1137761323.8800.5.camel@localhost.localdomain> > Kjartan Maraas <km...@br...> wrote: > > > I reported a bug wrt leaks in the new memory allocator in Glib and the > > comments in the bugreport ended like this: > > > > "to me it looks like valgrind needs better support for > > pthread_setspecific(3)." > > > > Can anyone take a look at the bugreport and tell me if I should file a > > bug against valgrind for this issue? > > > > Report his here: > > http://bugzilla.gnome.org/show_bug.cgi?id=324438 > > You don't say what version of valgrind you're using, but no recent > version knows anything about any part of pthreads - it works at a > lower level than that. > Ok, sorry about that. I'm using valgrind from SVN as of 18th of january. > Specifically, for thread specific data, it will simply see the system > fiddling with the LDT and/or GDT and take the appropriate actions. > I'll try to get more details on this then to figure out if the leaks are real or if valgrind is confused. Cheers Kjartan |