SIGABRT due double free

[Fernando Apesteguía <fernando apesteguia gmail com>]

Thanks, now it appears to works fine.

I thought gtk was completly thread safe, but is logic tu use a method
for mutual exclusion. Really thanks a lot.
We'll meet in my next post :)

Best regards!!

---------- Forwarded message ----------
From: Andreas Stricker <andreas stricker fela ch>
Date: 24-nov-2005 9:27
Subject: Re: SIGABRT due double free
To: gtk-app-devel-list gnome org


Fernando ApesteguXa schrieb:
> I'm developing a gtk/gnome application with two threads. An schema of
> the application is this:
[SNIP]
> thread_func is updating data periodically with a sleep pause.
> At this point, I suppose the other thread is catching events normally
> (in fact, tabs of the notebook changes without problems). Well, at
> short time from run app, I get:
>
> *** glibc detected *** double free or corruption (!prev): 0x00000000006115a0 ***
> Program received signal SIGABRT, Aborted.
[SNIP]
> The curious thing is that I _have not_ any free, realloc or malloc in
> my code, only those that gtk/glib functions like g_file_get_contents
> can perform.

This looks like a race condition due missing mutual exclusion.
Did you read the API documentation and the various tutorials?

http://www.gtk.org/api/2.6/gdk/gdk-Threads.html

Cheers,

Andy
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list