GNU bug report logs - #7517
24.0.50; repeated crash under Mac OS X

Previous Next

Packages: ns, emacs;

Reported by: emacs user <user.emacs <at> gmail.com>

Date: Mon, 29 Nov 2010 14:30:03 UTC

Severity: normal

Found in version 24.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #104 received at 7517 <at> debbugs.gnu.org (full text, mbox):

From: Jan Djärv <jan.h.d <at> swipnet.se>
To: emacs user <user.emacs <at> gmail.com>
Cc: "Uday S. Reddy" <u.s.reddy <at> cs.bham.ac.uk>, cyd <at> stupidchicken.com,
	emacs-devel <at> gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>,
	7517 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#7517: 24.0.50; repeated crash under Mac OS X
Date: Fri, 31 Dec 2010 23:30:31 +0100
On Fri, Dec 31, 2010 at 6:56 PM, Stefan Monnier
<monnier <at> iro.umontreal.ca>  wrote:
>> Emacs should never use unibyte strings for buffer names.
>
> I don't think we make any effort to prevent this from happening.
>
> And I'm not completely sure that it would be worth the trouble either:
> I suspect that wherever a unibyte buffer-name would cause problem
> (mode-line, window title, younameit), some other unibyte string could
> appear from elsewhere just as well, so enforcing multibyte buffer-names
> wouldn't close the vulnerabilities.

If we don't at least ENCODE_UTF_8 should do the right thing.  Is the coding 
for these kind of strings known?  If not and we don't enforce encoding in 
basic interfaces, we must deal with all existing encodings?

	Jan D.





This bug report was last modified 14 years and 143 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.