RE: g_list_append() giving SEGV
- From: "Aggarwal , Ajay" <ajay crossbeamsys com>
- To: "'Dugas, Alan'" <alan dugas analog com>
- Cc: "'gtk-list gnome org'" <gtk-list gnome org>
- Subject: RE: g_list_append() giving SEGV
- Date: Mon, 9 Oct 2000 13:43:36 -0400
Thats exactly how I am using it. Do you know any place where it is
documented clearly as to which calls from Glib are thread-safe (or not
Thanks in advance
> -----Original Message-----
> From: Dugas, Alan [mailto:alan dugas analog com]
> Sent: Monday, October 09, 2000 1:35 PM
> To: Aggarwal , Ajay
> Subject: RE: g_list_append() giving SEGV
> g_list_append() may move the address of the list you pass it.
> You might
> want to check to make sure that after every g_list_append()
> call, you update
> any variables that are supposed to track it.
> i.e. glist_variable = g_list_append(glist_variable, "user data");
> Hope this helps.
> -- Stupid Genius
> > ----------
> > From: Aggarwal , Ajay[SMTP:ajay crossbeamsys com]
> > Sent: Monday, October 09, 2000 12:51 PM
> > To: 'gtk-list gnome org'
> > Subject: g_list_append() giving SEGV
> > Does anybody know if glib-1.2.6-3 is thread-safe in
> general? I am getting
> > a
> > SEGV in g_list_append() call. I am doing g_thread_init() in the very
> > beginning of my program and g_thread_supported() returns TRUE after
> > g_thread_init() call.
> > The backtrace looks like:
> > g_list_append()
> > g_list_alloc()
> > g_mem_chuck_alloc()
> > g_malloc()
> > _libc_malloc()
> > chuck_alloc()
> > chunk_free()
> > Thanks.
> > Ajay
> > _______________________________________________
> > gtk-list mailing list
> > gtk-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gtk-list
] [Thread Prev