From: Juri Linkov <juri@jurta.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: Crashes with non-default language environments
Date: Mon, 11 Feb 2008 00:48:40 +0200 [thread overview]
Message-ID: <87prv4l96f.fsf@jurta.org> (raw)
In-Reply-To: <jwvmyq97ecd.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 09 Feb 2008 21:09:04 -0500")
>> This crash is caused by the corrupt byte-code produced by
>> `byte-compile-lapcode'. `string-make-unibyte' at the end of this
>> function produces different bytecode strings in different
>> language environments. This problem can be narrowed down to:
>
> Shouldn't it be string-to-unibyte instead?
I've just checked that `string-as-unibyte' produces even worse results
than `string-make-unibyte'. It replaces every byte in the original
string with 2-byte sequences.
The change to use `string-as-unibyte' came from the Unicode branch:
2008-02-02 Kenichi Handa <handa@m17n.org>
* emacs-lisp/bytecomp.el (byte-compile-lapcode): Be sure to
return a unibyte string.
Maybe, this change is correct, but the bug is in the definition of the
language environment, I can't say for sure. Comparing results of calling
`string-make-unibyte' on 256 bytes in different language environments
gives only 6 differences:
\240 -> \232
\251 -> \277
\260 -> \234
\262 -> \235
\267 -> \236
\367 -> \237
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2008-02-10 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 19:54 Crashes with non-default language environments Juri Linkov
2008-02-09 22:17 ` Juri Linkov
2008-02-10 2:09 ` Stefan Monnier
2008-02-10 22:48 ` Juri Linkov [this message]
2008-02-11 1:39 ` Stefan Monnier
2008-02-11 1:56 ` Miles Bader
2008-02-11 3:02 ` Stefan Monnier
2008-02-11 4:11 ` Miles Bader
2008-02-11 14:06 ` Stefan Monnier
2008-02-11 15:16 ` Miles Bader
2008-02-11 16:51 ` Stefan Monnier
2008-02-11 21:27 ` Juri Linkov
2008-02-12 11:41 ` Kenichi Handa
2008-02-12 16:29 ` Stefan Monnier
2008-02-12 11:23 ` Kenichi Handa
2008-02-12 19:29 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87prv4l96f.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).