[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ["Eli Zaretskii" <address@hidden>] Re: crash in emacs-21.1
From: |
Gerd Moellmann |
Subject: |
Re: ["Eli Zaretskii" <address@hidden>] Re: crash in emacs-21.1 |
Date: |
25 Oct 2001 10:56:25 +0200 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.1.50 |
address@hidden (Pavel Janík) writes:
> From: address@hidden (Gerd Moellmann)
> Date: 25 Oct 2001 10:16:24 +0200
>
> > > The files are all compiled with 20.2. I haven't been following the
> > > 20.x line closely because I worked on what's now 21 during that time,
> > > but ISTR that there was something affecting the byte-code around
> > > 20.2. Does else someone remember that?
> >
> > I remember that, but I couldn't find any trace of it in NEWS.
>
> Does this help?
>
> alloc.c:
>
> if (STRINGP (args[1]) && STRING_MULTIBYTE (args[1]))
> /* BYTECODE-STRING must have been produced by Emacs 20.2 or the
> earlier because they produced a raw 8-bit string for byte-code
> and now such a byte-code string is loaded as multibyte while
> raw 8-bit characters converted to multibyte form. Thus, now we
> must convert them back to the original unibyte form. */
> args[1] = Fstring_as_unibyte (args[1]);
Hm, maybe that comment was what I remembered. Could there conceivably
go something wrong in 21 with this conversion? The report was that
apparently a particular set of files compiled with 20.2 (I have a tar)
makes Fbyte_code crash.