[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: crash in emacs-21.1
From: |
Sadinoff, Daniel |
Subject: |
RE: crash in emacs-21.1 |
Date: |
Wed, 24 Oct 2001 10:47:21 -0400 |
but we don't enable BYTE_CODE_SAFE by default?
anyway, here's the code in question. Note that it's quite old, circa 1998.
http://www.sadinoff.com/tmp/bad-cc.tar.gz
-----Original Message-----
From: Andreas Schwab [mailto:schwab@suse.de]
Sent: Wednesday, October 24, 2001 10:37 AM
To: Eli Zaretskii
Cc: Sadinoff, Daniel; Pavel Janík; bug-gnu-emacs@gnu.org
Subject: Re: crash in emacs-21.1
Eli Zaretskii <eliz@is.elta.co.il> writes:
|> On Wed, 24 Oct 2001, Sadinoff, Daniel wrote:
|>
|> > Just to be clear here, I understand that there's an interoperability
problem
|> > with xemacs-compiled elc's, but is there the expectation that GNU
emacs-21
|> > should be able to cleanly load anything byte-compiled with
GNU-emacs-20?
|>
|> I'm not really sure what is the official say-so on this (could people who
|> know the byte compiler better than I do please help?)
IMHO the byte compiler should be upward compatible, and also crash safe.
Unfortunately, the function byte-code only does full checking if
BYTE_CODE_SAFE is defined, such that you can get undefined behaviour
(which may include crashing) if you pass an invalid bytecode string.
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
- Re: crash in emacs-21.1, (continued)
- Re: crash in emacs-21.1, Eli Zaretskii, 2001/10/24
- RE: crash in emacs-21.1, Sadinoff, Daniel, 2001/10/23
- RE: crash in emacs-21.1, Sadinoff, Daniel, 2001/10/24
- RE: crash in emacs-21.1, Sadinoff, Daniel, 2001/10/24
- RE: crash in emacs-21.1,
Sadinoff, Daniel <=