[debbugs-tracker] bug#21592: closed (25.0.50; Fatal error)

[GNU bug Tracking System]

Your message dated Fri, 9 Oct 2015 20:58:33 +0200
with message-id <address@hidden>
and subject line Re: bug#21592: 25.0.50; Fatal error
has caused the debbugs.gnu.org bug report #21592,
regarding 25.0.50; Fatal error
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
21592: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21592
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: 25.0.50; Fatal error Date: Wed, 30 Sep 2015 12:55:03 +0200

Recipe from "emacs -Q":

  1. M-x show-paren-mode <RET>

  2. Visit the attached file.

  3. Type something at the end of line 3 (so that the following paragraph
    gets highlighted - This seems like a different but, BTW)

  4. M->

At that moment, I see the "Emacs Abort Dialog", saying that "A fatal
error has occurred!".

FWIW, I've reproduced the above crash in two different machines: one
with Windows 7 and other with Windows Server 2003 R2.

------------

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2015-09-23
Repository revision: 325200ac1dcf5bed6918ea827d8a48d89487e083
Windowing system distributor 'Microsoft Corp.', version 6.1.7601
Configured using:
 'configure --host=i686-pc-mingw32 --enable-checking=yes,glyphs'

Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB
TOOLKIT_SCROLL_BARS

Important settings:
  value of $LANG: ESN
  locale-coding-system: cp1252


-- 
Dani Moncayo

file1
Description: Binary data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#21592: 25.0.50; Fatal error
>
>
>
>
> Date: 
>
> Fri, 9 Oct 2015 20:58:33 +0200
>
>
>
>
> > I confirm that, with the current development sources, the fatal error
> > is gone.
> >
> > But I still see something that I consider a bug: From "emacs -Q", just
> > visit the file I attached in my initial post.  The heredoc is
> > displayed initially without highlighting.  To get it highlighted, I
> > have to do something like, for example, writing something on line 3.
>
> I've tried the current master branch, and the above remaining problem seems to
> be fixed too.  So I'm closing this bug report.
>
> Thank you.
>
> -- 
> Dani Moncayo
>
>
> --- End Message ---