bug#21592: 25.0.50; Fatal error

bug#21592: 25.0.50; Fatal error

[Dani Moncayo]

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

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

[-- Attachment #2: file1 --]
[-- Type: application/octet-stream, Size: 126 bytes --]

#!/bin/sh

# Blah

dbaccess mapfrebd - - <<EOF
UNLOAD TO sel_mdentidad.unl
SELECT * FROM mdentidad WHERE entidad IN ($2);
EOF

bug#21592: 25.0.50; Fatal error

[Dani Moncayo]

BTW, this problems does _not_ happen in my previous build of Emacs.  This one:

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


-- 
Dani Moncayo

bug#21592: 25.0.50; Fatal error

[Eli Zaretskii]

> Date: Wed, 30 Sep 2015 12:55:03 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> 
> 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!".

It doesn't happen to me here.  Can you run under GDB and show a
backtrace from the abort?

bug#21592: 25.0.50; Fatal error

[Xue Fuqiao]

I'm not able to reproduce this problem (there's no crash/error).  Here's
some info about my Emacs/machine:

In GNU Emacs 25.0.50.6 (x86_64-apple-darwin14.5.0, NS appkit-1348.17
Version 10.10.5 (Build 14F27))
 of 2015-09-26
Repository revision: 188f657a827b04d72376f8b483c7d4b678e96fac
Windowing system distributor 'Apple', version 10.3.1404
Configured features:
ACL LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS

Important settings:
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Shell-script

Minor modes in effect:
  sh-electric-here-document-mode: t
  show-paren-mode: t
  tooltip-mode: t
  global-eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Show-Paren mode enabled
Quit
Setting up indent for shell type sh
Indentation variables are now local.
Indentation setup for shell type sh

Load-path shadows:
None found.

Features:
(shadow sort gnus-util mail-extr emacsbug message dired format-spec
rfc822 mml mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231
mailabbrev gmm-utils mailheader sendmail rfc2047 rfc2045 ietf-drums
mm-util help-fns help-mode easymenu cl-loaddefs pcase cl-lib mail-prsvr
mail-utils sh-script smie executable cus-start cus-load paren time-date
mule-util tooltip eldoc electric uniquify ediff-hook vc-hooks
lisp-float-type mwheel ns-win term/common-win tool-bar dnd fontset image
regexp-opt fringe tabulated-list newcomment elisp-mode lisp-mode
prog-mode register page menu-bar rfn-eshadow timer select scroll-bar
mouse jit-lock font-lock syntax facemenu font-core frame cl-generic cham
georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech
european ethiopic indian cyrillic chinese charscript case-table epa-hook
jka-cmpr-hook help simple abbrev minibuffer cl-preloaded nadvice
loaddefs button faces cus-face macroexp files text-properties overlay
sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote cocoa ns multi-tty
make-network-process emacs)

bug#21592: 25.0.50; Fatal error

[Dani Moncayo]

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

> It doesn't happen to me here.  Can you run under GDB and show a
> backtrace from the abort?

I'm attaching the output of "thread apply all bt".

Let me know if you need more data.

Thanks.

-- 
Dani Moncayo

[-- Attachment #2: gdb.zip --]
[-- Type: application/zip, Size: 2754 bytes --]

bug#21592: 25.0.50; Fatal error

[Eli Zaretskii]

> Date: Thu, 1 Oct 2015 22:39:44 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: 21592@debbugs.gnu.org
> 
> > It doesn't happen to me here.  Can you run under GDB and show a
> > backtrace from the abort?
> 
> I'm attaching the output of "thread apply all bt".

Thread 1 (Thread 3644.0x15cc):
#0  0x75608ef3 in KERNELBASE!DebugBreak ()
   from C:\Windows\SysWOW64\KernelBase.dll
#1  0x011add0d in emacs_abort () at C:/emacs/src/repo/src/w32fns.c:9412
#2  0x010c8ccd in terminate_due_to_signal (sig=sig@entry=22, 
    backtrace_limit=backtrace_limit@entry=2147483647)
    at C:/emacs/src/repo/src/emacs.c:397
#3  0x011262b2 in die (
    msg=msg@entry=0x1461a3c <format.29657+1544> "charpos >= syntax_propertize__done", 
    file=file@entry=0x14619ec <format.29657+1464> "C:/emacs/src/repo/src/syntax.c", line=line@entry=512) at C:/emacs/src/repo/src/alloc.c:6951
#4  0x0117201d in update_syntax_table_forward (charpos=52, init=false, 
    object=0) at C:/emacs/src/repo/src/syntax.c:512
#5  0x011723c4 in UPDATE_SYNTAX_TABLE_FORWARD (charpos=<optimized out>)
    at C:/emacs/src/repo/src/syntax.h:179
#6  UPDATE_SYNTAX_TABLE (charpos=52) at C:/emacs/src/repo/src/syntax.h:199
#7  char_quoted (charpos=<optimized out>, charpos@entry=52, bytepos=51, 
    bytepos@entry=52) at C:/emacs/src/repo/src/syntax.c:550
#8  0x0117902d in scan_lists (from=52, count=-1, depth=0, sexpflag=true)
    at C:/emacs/src/repo/src/syntax.c:2963

I have no idea what this means, perhaps Stefan can help.

Do you see this crash in a non-optimized build?  If so, please show a
backtrace from that build.

Thanks.

bug#21592: 25.0.50; Fatal error

[Stefan Monnier]

> #3  0x011262b2 in die (
>     msg=msg@entry=0x1461a3c <format.29657+1544> "charpos >= syntax_propertize__done", 

Sounds like the bug I fixed in 4c0fed13e5ca1826bab52cd9c3fc31ad0e5c765c
(installed on Sep 23).


        Stefan

bug#21592: 25.0.50; Fatal error

[Eli Zaretskii]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Dani Moncayo <dmoncayo@gmail.com>,  21592@debbugs.gnu.org
> Date: Thu, 01 Oct 2015 20:40:55 -0400
> 
> > #3  0x011262b2 in die (
> >     msg=msg@entry=0x1461a3c <format.29657+1544> "charpos >= syntax_propertize__done", 
> 
> Sounds like the bug I fixed in 4c0fed13e5ca1826bab52cd9c3fc31ad0e5c765c
> (installed on Sep 23).

Thanks.  Dani, please update and see if the problem is still there.

bug#21592: 25.0.50; Fatal error

[Dani Moncayo]

> Thanks.  Dani, please update and see if the problem is still there.

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.

And oddly enough, if I then kill the buffer and re-visit the file,
this time the heredoc is highlighted from the beginning.

--
Dani Moncayo

bug#21592: 25.0.50; Fatal error

[Dani Moncayo]

> 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