From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 31245@debbugs.gnu.org
Subject: bug#31245: 27.0.50; Crash in Windows emacs
Date: Wed, 02 May 2018 17:49:04 +0300 [thread overview]
Message-ID: <838t92qfj3.fsf@gnu.org> (raw)
In-Reply-To: <vz1bmdzgl2z.fsf@gmail.com> (message from Andy Moreton on Tue, 01 May 2018 21:47:00 +0100)
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Tue, 01 May 2018 21:47:00 +0100
>
> On Mon 23 Apr 2018, Andy Moreton wrote:
>
> > On Mon 23 Apr 2018, Eli Zaretskii wrote:
> >> Thanks, but this kind of problems is impossible to debug without a
> >> reproducer. Can you come up with one?
>
> I still cannot use a debugger on this system, but I have collected two
> more backtraces from emacs built with the same options as before, from
> changeset 65ac27783a959a8339c2aab0f1e54d9b508a1f1f on master.
>
> In both of these I was typing in an rnc-mode buffer (for a Relax-NG
> schema), and it crashed while I typed OSVERSION as an element name in
> the schema (only the O was displayed). The file is plain ascii.
Thanks. There's no need to run Emacs under a debugger in this case,
AFAIU. What is needed is a recipe that would more or less reliably
reproduce the problem. The place where the assertion is violated and
why Emacs aborts is quite clear; what is missing is the root cause of
that impossible situation. And that can only be provided by a recipe.
Can you describe what should one do to reproduce this problem,
starting from "emacs -Q", loading rnc-mode and anything else that is
needed, then typing or evaluating something that causes the crash?
next prev parent reply other threads:[~2018-05-02 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 13:51 bug#31245: 27.0.50; Crash in Windows emacs Andy Moreton
2018-04-23 15:28 ` Eli Zaretskii
2018-04-23 15:47 ` Andy Moreton
2018-05-01 20:47 ` Andy Moreton
2018-05-02 14:49 ` Eli Zaretskii [this message]
2018-05-21 17:51 ` Andy Moreton
2018-05-21 19:12 ` Eli Zaretskii
2018-05-21 19:43 ` Eli Zaretskii
2019-09-26 19:30 ` Lars Ingebrigtsen
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=838t92qfj3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31245@debbugs.gnu.org \
--cc=andrewjmoreton@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).