Hi Antonio, Antonio Radici wrote:
> Despite the bad state we don't expect mutt to segfault :( > have you got any core for that problem? Is it reproducible in any way? It seems to have something to do with (interrupted?) deletion of a message and arrival of a new message with caching enabled. Wasn't this the one where a loop counter was reused and not properly initialized the second time it was used? I seem to remember a patch floating around (probably the one from message 95) which worked. See http://bugs.debian.org/626879 for a backtrace. Sorry I don't have any more definitive information --- the laptop I normally use is dead at the moment. Jonathan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
