On Tuesday, November 29, 2005 at 8:59:01 +0800, WANG Xu wrote:
> the segfault occured even in:
>| LANG=en_US
>| LC_CTYPE=zh_CN.GBK
The charset of all the categories must be the same as the terminal,
or strictly compatible. In your case only GBK or US-Ascii. That en_US
having an implicit Latin-1 charset is conflicting: You should remove
LC_CTYPE, and set back LANG=zh_CN.GBK. Does it still segfault? Yes.
Now try with "set thorough_search=yes" in muttrc. Does it still
segfault? Not anymore?
> I am sorry for the annoying
No problem, GDB is not an easy tool at first encounter. :-)
> #0 0xb7d0b5ef in memcpy () from /lib/tls/libc.so.6
> #1 0xb7d3ca52 in re_set_registers () from /lib/tls/libc.so.6
> #2 0xb7d3cd15 in re_set_registers () from /lib/tls/libc.so.6
> #3 0xb7d5074a in re_compile_pattern () from /lib/tls/libc.so.6
> #4 0xb7d51beb in regexec () from /lib/tls/libc.so.6
> #5 0xb7daaf1c in regexec () from /lib/tls/libc.so.6
Looks like my hypothesis was not so bad. So it's another instance of
glibc regexp invalid multibyte segfault, now in 2.3.5-6. Probably you
can also segfault outside of Mutt, doing things like:
| $ printf "\xE9" | grep "^Subject.*"
If confirmed, probably this bug will have to be reassigned. ¿Dato?
Bye! Alain.
--
set honor_followup_to=yes in muttrc is the default value, and makes your
list replies go where the original author wanted them to go: Only to the
list, or with a private copy.
