* Alain Bench <[EMAIL PROTECTED]> wrote: > On Friday, October 13, 2006 at 23:53:27 +0200, Georg Neis wrote: > > > % mutt -f crash > > Sorting mailbox...zsh: segmentation fault (core dumped) mutt -f crash > > Unreproducible here. Could you please check the backtrace? Let > segfault create a core, gdb $(which mutt) core, then type "bt" and > "quit".
I doubt that it will help you much since mutt is compiled without debugging symbols: #0 0xb7c63c1f in memcpy () from /lib/tls/libc.so.6 #1 0x080b2765 in ?? () #2 0xbf98a5e3 in ?? () #3 0xbf989eac in ?? () #4 0xfffffff8 in ?? () #5 0x08078c50 in ?? () #6 0xbf98a460 in ?? () #7 0x00000064 in ?? () #8 0xbf98a2ac in ?? () #9 0xbf98a460 in ?? () #10 0x00000064 in ?? () #11 0x00000000 in ?? () If I find some time, I'll try to build a version with debugging information. > BTW to send attached such offending mails, better use > <attach-message> (bound to 'A' by default) than <attach-file> (bound to > 'a' by default) in Mutt when applicable. Or even better here: Zip the > example mbox and attach the zipfile. This avoids any corruption, > transcoding, and added charset ambiguity. Thanks for the tip. However, I've just downloaded the attachment (since I no longer had the file on my disk) and could immediately reproduce the crash. > Anyway the problem seems to come from raw hibit bytes in the header. > I can't be sure of the used charset, but wild guess it could be BIG-5. > Does it segfault when you set: > > | unset strict_mime > | set assumed_charset=big-5 > > Does it segfault when you set a more generic: > > | unset strict_mime > | set assumed_charset=cp1252 Yes, mutt crashs in both cases. Thanks for taking care, Georg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
