GNU bug report logs -
#36507
27.0.50; Crash on evaluating invalid UTF-8 byte sequence on MacOS
Previous Next
Reported by: Stefan Kangas <stefan <at> marxist.se>
Date: Fri, 5 Jul 2019 02:05:02 UTC
Severity: normal
Found in version 27.0.50
Done: YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp> writes:
> > > (decode-coding-string "\xE3\x32\x9A\x36" 'chinese-gb18030)
> >
> > I think the issue as such is beyond me, but I can reproduce this every time.
> > Please let me know if you need help testing or more information.
> >
> > Before crash, I get this output:
> > Thread 1 received signal SIGSEGV, Segmentation fault.
> > 0x00007fff8ddbd326 in CFCharacterSetIsLongCharacterMember () from
> > /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
>
> Please try the patch below.
The patch works; I no longer get the crash. The return value is now:
"#(" " 0 1 (charset gb18030-4-byte-ext-2))"
Note that the " " is a visually wide white space character that I
can't copy to other programs for some reason. It is here replaced
with a space. Not sure if this is expected or not.
Thank you for providing a fix so swiftly.
Best regards,
Stefan Kangas
This bug report was last modified 5 years and 316 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.