Hi Carlos,

On 06/28/2012 06:25:29 PM Thu, Peter Bloomfield wrote:
Carlos,

On 06/27/2012 12:26:21 PM Wed, Carlos Franke wrote:
Both stack traces suggest that it's a locking issue: main thread holding lock A and 
asking for lock B, while a subthread holds lock B and asks for lock A. Identifying A and 
B is difficult, however, because the traces have no debugging information from Balsa. 
Could you rebuild Balsa to include it? Perhaps 'make CFLAGS="-g -O2"'?

Of course, see below.

Thanks! I can reproduce the problem, if I do not save my IMAP account password, 
and set up INBOX to be opened on start-up.

But reproducing it leaves me a long way from finding a fix! More anon...

All I can suggest for now is to build with --disable-threads. In a threaded 
build, certain use-cases currently lead to deadlocks like yours and Paweł's. 
We're working on it--sorry for the inconvenience.

Best,

Peter

Attachment: pgpuQAV22x8Bt.pgp
Description: PGP signature

_______________________________________________
balsa-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/balsa-list

Reply via email to