unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24206@debbugs.gnu.org
Subject: bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault
Date: Thu, 11 Aug 2016 23:51:41 +0000	[thread overview]
Message-ID: <CAArVCkQq6oU+qpoQrC2+CipGYiGDYfac6BB4a+zMWUxTPvyXSg@mail.gmail.com> (raw)
In-Reply-To: <83y443dqbv.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

Eli Zaretskii <eliz@gnu.org> schrieb am Do., 11. Aug. 2016 um 13:05 Uhr:

> > From: Phil <p.stephani2@gmail.com>
> > Date: Thu, 11 Aug 2016 11:55:05 -0700
> >
> >
> > Build is from the emacs-25 branch.
> >
> > $ ./emacs -Q -eval "(progn (defface test nil \"\`\\240'\")
> (customize-face 'test))"
> >
> > character.h:703: Emacs fatal error: assertion failed: CHAR_VALID_P (ch)
> > Fatal error 6: Aborted
> >
> > I think this is serious enough to be release-blocking.  Seen in the wild
> > with older versions of show-wspace.el.
>
> Please show the real-life example where this rears its ugly head.  The
> recipe (which is appreciated) is obscure enough to be easily avoided,
> so it doesn't yet convince me this should block a release.  There's
> always one more crash out there.
>
>
Ubuntu Trusty Tahr (supported until 2019) contains a package
emacs-goodies-el, which contains a file show-wspace.el, which contains a
face with the docstring "*Face for highlighting non-breaking spaces
(`\240')in Font-Lock mode." Attempting to customize that face leads to the
segfault.

[-- Attachment #2: Type: text/html, Size: 1585 bytes --]

  reply	other threads:[~2016-08-11 23:51 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 18:55 bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault Phil
2016-08-11 20:05 ` Eli Zaretskii
2016-08-11 23:51   ` Philipp Stephani [this message]
2016-08-13  8:32     ` Eli Zaretskii
2016-08-13 12:25       ` Nicolas Petton
2016-08-14  6:33         ` John Wiegley
2016-08-14  4:54 ` Paul Eggert
2016-08-14 14:27   ` Eli Zaretskii
2016-08-14 14:51     ` Paul Eggert
2016-08-14 17:18       ` Eli Zaretskii
2016-08-15  2:04         ` Paul Eggert
2016-08-15 16:09           ` Eli Zaretskii
2016-08-15 16:46             ` Andreas Schwab
2016-08-15 18:43               ` Paul Eggert
2016-08-15 19:04                 ` Eli Zaretskii
2016-08-15 18:51               ` Eli Zaretskii
2016-08-15 19:05                 ` John Wiegley
2016-08-15 20:41                 ` Paul Eggert
2016-08-16 14:38                   ` Eli Zaretskii
2016-08-16 15:25                     ` John Wiegley
2016-08-16 16:09                       ` Nicolas Petton
2016-08-18 16:30                       ` Nicolas Petton
2016-08-18 16:41                         ` John Wiegley
2016-08-18 17:35                           ` Eli Zaretskii
2016-08-16 17:37                     ` Paul Eggert
2016-08-16 17:45                       ` John Wiegley
2016-08-16 17:55                         ` Paul Eggert
2016-08-16 17:57                           ` John Wiegley
2016-08-16 18:44                           ` Dmitry Gutov
2016-08-16 18:31                       ` Eli Zaretskii
2016-08-16 14:52                   ` Eli Zaretskii
2016-08-16 21:07                     ` Paul Eggert
2016-08-17 15:12                       ` Eli Zaretskii
2016-08-17 17:41                         ` Paul Eggert
2016-08-17 18:06                           ` Eli Zaretskii
2016-08-17 20:52                             ` Paul Eggert
2016-08-18 14:30                               ` Eli Zaretskii
2016-08-18 18:33                                 ` Paul Eggert
2016-08-18 18:58                                   ` Eli Zaretskii
2016-08-17 17:50                       ` Dmitry Gutov
2016-08-14 15:21   ` Dmitry Gutov
2016-08-15  1:53     ` Paul Eggert
2016-08-15  1:57       ` Dmitry Gutov
2016-08-15  2:05         ` Paul Eggert
2016-08-14 17:21   ` Eli Zaretskii
2016-08-14 20:16     ` Paul Eggert
2016-08-15  1:12       ` Paul Eggert

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=CAArVCkQq6oU+qpoQrC2+CipGYiGDYfac6BB4a+zMWUxTPvyXSg@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=24206@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).