From: Eli Zaretskii <eliz@gnu.org>
To: sudarshan@acm.org
Cc: 24417@debbugs.gnu.org
Subject: bug#24417: 25.1; Emacs crashes during gc
Date: Thu, 29 Sep 2016 18:47:28 +0300 [thread overview]
Message-ID: <8337kioghb.fsf@gnu.org> (raw)
In-Reply-To: <CAAc3KwyCKoZefkz=MZcvwtL=RXWdtBbxBjjWwJsDeCBhf59H+A@mail.gmail.com> (message from Sudarshan Gaikaiwari on Wed, 28 Sep 2016 19:50:42 -0500)
> From: Sudarshan Gaikaiwari <sudarshan@acm.org>
> Date: Wed, 28 Sep 2016 19:50:42 -0500
> Cc: 24417@debbugs.gnu.org
>
> y emacs process crashed again. I was running a debug build as part of
> bug#24417. The back trace indicates that the sefault is in a different
> module. Please let me know if I should file a new bug instead of
> updating this one.
> I was trying to run rgrep when this crash occured. The emacs build is
> of RC2 and not
> the latest release.
This crash looks differently, but I'm not yet sure if it's a separate
problem, so let's keep them together for now.
Is this debugging session still alive? If so, I'd like to ask you to
report values of some relevant variables.
What seems to have happened here is that Emacs was going to report an
error by starting the Lisp debugger. Then, while redrawing the
display triggered by that, some font-lock construct caused the display
engine to call a Lisp function, which eventually called
re-search-forward, and that segfaulted because it got an invalid
string pointer.
It would be good to know what was the error Emacs wanted to report,
and what function was invoked from redisplay that caused the crash.
next prev parent reply other threads:[~2016-09-29 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 2:20 bug#24417: 25.1; Emacs crashes during gc sudarshan
2016-09-12 16:49 ` Eli Zaretskii
2016-09-12 18:00 ` Sudarshan Gaikaiwari
2016-09-12 18:43 ` Eli Zaretskii
2016-09-29 0:50 ` Sudarshan Gaikaiwari
2016-09-29 15:47 ` Eli Zaretskii [this message]
2016-09-29 16:11 ` Sudarshan Gaikaiwari
2016-09-30 7:36 ` Eli Zaretskii
2016-09-30 15:05 ` Sudarshan Gaikaiwari
2016-12-07 20:33 ` Glenn Morris
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=8337kioghb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24417@debbugs.gnu.org \
--cc=sudarshan@acm.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).