Re: glib memory allocation problems
- From: Tim Janik <timj gtk org>
- To: Miklos Szeredi <miklos szeredi hu>
- Cc: jimis gmx net, Gtk+ Developers <gtk-devel-list gnome org>
- Subject: Re: glib memory allocation problems
- Date: Tue, 15 May 2007 22:09:27 +0200 (CEST)
On Tue, 15 May 2007, Miklos Szeredi wrote:
And this is perfectly possible if program is using the pthread API,
while using glib for hash tables, etc.
if you use the pthread API without calling g_thread_init(), you're getting
yourself into trouble. don't do that, glib can't possibly work correctly
in threaded scenarios without its threading system being initialized.
I know that. Now.
What I was suggesting is that glib should try to warn the user in such
Possibly only if G_SLICE=debug-blocks is set or whatever. It doesn't
seem all that difficult: when accessing thread specific data, compare
with the last thread id.
it *is* that difficult. there are a lot of things that will break if
you expect glib to be thread safe without initializing threading.
if you can come up with a patch that catches all cases (uses of mutexes,
conditions, private data, thread methods, ...) without impacting
(slowing down) the common uses, please file it in our bugzilla.
] [Thread Prev