On opening certain messages I see a reproducible: Program received signal SIGSEGV, Segmentation fault. 0x420c450a in find_collation_sequence_value () from /lib/tls/libc.so.6 (gdb) bt #0 0x420c450a in find_collation_sequence_value () from /lib/tls/libc.so.6 #1 0x420c42f9 in check_node_accept_bytes () from /lib/tls/libc.so.6 #2 0x420c0df2 in transit_state_mb () from /lib/tls/libc.so.6 #3 0x420c0703 in transit_state () from /lib/tls/libc.so.6 #4 0x420be0ca in check_matching () from /lib/tls/libc.so.6 #5 0x420bd93b in re_search_internal () from /lib/tls/libc.so.6 #6 0x420bce67 in regexec () from /lib/tls/libc.so.6 #7 0x0807cbeb in strcpy () #8 0x0807e1f5 in strcpy () #9 0x0807e87c in strcpy () #10 0x08054967 in strcpy () #11 0x0805db6d in strcpy () #12 0x08072655 in strcpy () #13 0x42015704 in __libc_start_main () from /lib/tls/libc.so.6 According to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=261135 this is a glibc bug. mutt-1.4.1-3.3 glibc-2.3.2-27.9.7
glibc-2.3.2-27.9.7 is not Fedora Core 2, but RHL9. In Fedora Core 2 #114839 is fixed, and the reproducer in debian bug database doesn't crash either.
Ah, sorry, my bad, didn't realize I was running mutt on a wrong machine! :-(