From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 29326@debbugs.gnu.org
Subject: bug#29326: 26.0.90; Emacs crash on running comment-dwim
Date: Fri, 17 Nov 2017 09:03:52 +0200 [thread overview]
Message-ID: <83efoxidyf.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY0AOCqVXWSJ8bqyye-2=kgv52PqhRkTAR-JhctgOK3wxg@mail.gmail.com> (message from Kaushal Modi on Thu, 16 Nov 2017 19:43:00 +0000)
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Thu, 16 Nov 2017 19:43:00 +0000
>
> All of a sudden I can get emacs to crash consistently because of some rogue font lock regexp parsing
> between Org mode and nim-mode[1].
>
> I have attached a test file (that's the smallest I can get to from originally ~1000 line file). I can make the crash
> happen on doing M-x comment-dwim on line 69 (in the test.org file) but not on line 52 and earlier lines for
> example.
>
> [1]: https://github.com/nim-lang/nim-mode
>
> It will be tricky to get an emacs -Q recipe with org and nim-mode dependencies. So while I work on getting
> that recipe, does the below backtrace help?
The backtrace says that some Lisp changed the buffer contents in a
way that caused the window-start to become outside the accessible
portion of the buffer.
> Thread 1 "emacs" received signal SIGABRT, Aborted.
> 0x00000033e380f6ab in raise () from /lib64/libpthread.so.0
> (gdb) bt
> #0 0x00000033e380f6ab in raise () from /lib64/libpthread.so.0
> #1 0x000000000058c8f4 in terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:394
> #2 0x00000000006232d5 in die (msg=0x723428 "charpos < 0 || (charpos >= BUF_BEG (current_buffer) &&
> charpos <= ZV)", file=0x72313d "xdisp.c", line=2752) at alloc.c:7419
> #3 0x0000000000449caa in init_iterator (it=0x7fffffff22f0, w=0x888fb60, charpos=9982, bytepos=9982,
> row=0x7d9e430, base_face_id=DEFAULT_FACE_ID) at xdisp.c:2751
In this call frame #3, what is the value of ZV?
next prev parent reply other threads:[~2017-11-17 7:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 19:43 bug#29326: 26.0.90; Emacs crash on running comment-dwim Kaushal Modi
2017-11-17 7:03 ` Eli Zaretskii [this message]
2017-11-17 7:45 ` Eli Zaretskii
2017-11-17 17:11 ` Kaushal Modi
2017-11-17 18:06 ` Eli Zaretskii
2017-11-17 18:08 ` Kaushal Modi
2017-11-17 18:13 ` Kaushal Modi
2017-11-17 18:16 ` Noam Postavsky
2017-11-17 18:18 ` Kaushal Modi
2017-11-17 18:29 ` Eli Zaretskii
2017-11-17 18:36 ` Kaushal Modi
2017-11-17 19:46 ` Eli Zaretskii
2017-11-17 20:04 ` Kaushal Modi
2017-11-17 20:24 ` Eli Zaretskii
2017-11-17 20:29 ` Kaushal Modi
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=83efoxidyf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29326@debbugs.gnu.org \
--cc=kaushal.modi@gmail.com \
/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).