Re: [Bug: 21.5-b33] assert failed in rep_bytes_by_first_byte_1 -- bogus unicode?
Ar an cúigiú lá déag de mí Feabhra, scríobh Henry S. Thompson:
Steve Youngs <steve(a)sxemacs.org> writes:
> Henry S Thompson <ht(a)inf.ed.ac.uk> writes:
>
> > Crashed hard will trying to display spam under gnus.
>
> You can get some very nasty things in spam that really should never be
> foisted upon a poor unsuspecting text editor.
>
> I stopped seeing this sort of crash in Gnus about 10 years ago when I
> added the following rule to my ~/.procmailrc...
Thanks, but I have legitimate Chinese correspondents, not all known to
me in advance, so I really can't do that . . .
It’s unlikely to be a problem with the Unicode coding systems, given that we
don’t see it with other non-Chinese text, and that with Unicode it’s the
same code being exercised for non-Chinese and Chinese. It’s probably an
issue with the Big 5 coding system implementation, or possibly but a bit
less likely, with the ISO 2022 coding system implementation. The error
message shows the internal representation, but what we need is the external
representation plus the coding system that produced the internal
representation. We can work that out from the spam, if it’s available.
However, I'm already pre-processing some header lines -- is it
obvious
what the bogosity was in that string? I.e. can I filter this sort of
thing out before it crashes things? I'm not a coding-system
wizard. . .
--
‘Liston operated so fast that he once accidentally amputated an assistant’s
fingers along with a patient’s leg, […] The patient and the assistant both
died of sepsis, and a spectator reportedly died of shock, resulting in the
only known procedure with a 300% mortality.’ (Atul Gawande, NEJM, 2012)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta