On Monday, November 21, 2005 at 10:44:12 +0800, WANG Xu wrote:
> The failed mail is attached as mailfail.gz
It is a well-formed Latin-1 mail, with 1 e acute in "From:", and 2
in signature. As the e acute exists in GBK charset (printf "\xa8\xa6"),
the mail should be perfectly displayed.
> with `mutt -nF /dev/null', segfault occured when the latin-1 specific
> char in the mail was displayed.
I assume you mean the e acute in signature, or just before? So
segfault in pager scrolled down to nearly the end.
> While with the attached configure file `muttfail.gz', segfault occured
> when the ``From'' header was displayed
Interesting: In the past coloring regexps have already been found
to trigger glibc segfaults in specific conditions and locales. Now, it
would be the first time I hear this in a clean GBK setup... BTW there is
no need to end color header regexps by ".*": The full header is colored
anyway.
>| LANG=zh_CN.GBK
>| LC_ALL=zh_CN.GBK
>| $ echo $LANGUAGE
>| zh_CN.GBK
Bug or not bug, you should remove LC_ALL forever. And you should
also remove LANGUAGE: Does it still segfault?
> I am not familiar with gdb, and I followed your indication. I type the
> command above, then `run', after segfault, I `generate-core-file', and
> then `bt' and `quit'. Is this right?
Unfortunately I could not make use of the core. What I meant was:
-0) Verify "ulimit -c" prints "unlimited" for core files size.
-1) Use Mutt alone until segfault: A core file is created.
-2) Type "gdb /usr/bin/mutt core".
-3) At the GDB prompt type "bt" then "quit".
-4) Copy/paste us the text printed by GDB.
It should give us the function where the segfault occurred, and
calling functions.
Bye! Alain.
--
Everything about locales on Sven Mascheck's excellent site at new
location <URL:http://www.in-ulm.de/~mascheck/locale/>. The little tester
utility is at <URL:http://www.in-ulm.de/~mascheck/locale/checklocale.c>.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
