Re: Debian Bug#217642: balsa: exit with unread mail causes hang with 100% CPU usage



I've seen this kind of infinite loop when the memory allocator  
gets confused.  However, the stack trace doesn't help pin down  
the offending code, as the loop typically occurs later.  If you  
use:

MALLOC_CHECK_=2 gdb /path/to/balsa

you'll get an abort when the corruption occurs--could you post  
the results?

Thanks!

Peter



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]