On 12/16/2009 01:00:15 PM Wed, Pawel Salek wrote:
Hi,I could not reproduce the problem but...It looks like a memory corruption to me. Maybe the configuration is used by one thread while another is about to free() it? Do you think you could run balsa with MALLOC_CHECK_ environment variable set to 2? valgrind output would be even better!Pawel On 12/16/2009 06:09:41 PM, Jean-Luc Coulon (f5ibh) wrote:Hi, With the SVN version I've (very) frequently a segfault when I leave it
This looks like the same bug as in <URL:http://mail.gnome.org/archives/balsa-list/2009-July/msg00025.html>. I see it quite often myself--in gdb, it's always somewhere in malloc, and always results from a corrupt struct malloc_chunk, pointed to by victim.
I've used MALLOC_CHECK_ to try to find the corrupter, and also Valgrind, with no success. However it happens, it's below their respective radar screens.
Best, Peter
pgpN0uPj31IkZ.pgp
Description: PGP signature
_______________________________________________ balsa-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/balsa-list
