From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 31274@debbugs.gnu.org
Subject: bug#31274: 27.0.50; xdisp.c:7575: Emacs fatal error: assertion failed: IT_BYTEPOS (*it) == CHAR_TO_BYTE (IT_CHARPOS (*it))
Date: Sat, 28 Apr 2018 12:29:47 +0300 [thread overview]
Message-ID: <83h8nvu19w.fsf@gnu.org> (raw)
In-Reply-To: <jwv8t99bv5c.fsf@iro.umontreal.ca> (message from Stefan Monnier on Thu, 26 Apr 2018 15:54:55 -0400)
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Date: Thu, 26 Apr 2018 15:54:55 -0400
>
> Package: Emacs
> Version: 27.0.50
>
> I can reproduce the above assertion failure when I do the following:
>
> % src/emacs -Q /usr/bin/perl -l .../elpa/packages/nhexl-mode/nhexl-mode.el -f nhexl-mode --eval '(setq word-wrap t)'
> y
> M->
I cannot reproduce this, with today's master of Emacs and of ELPA. I
tried on GNU/Linux (in -nw) and on MS-Windows (in a GUI session), and
both didn't trigger the assertion (tried with 3 executables, including
those you mentioned). I'm guessing some particular byte sequence
present in your binaries triggers this. So please provide more
details.
P.S. I frequently wonder why veteran experienced users omit crucial
information from their bug reports, such as the C backtrace in this
case, that is very easy for them to collect. Please don't ever assume
that something which is 100% reproducible on your system can be
similarly easily reproduced on any other system, and that therefore
those details are an unnecessary luxury.
next prev parent reply other threads:[~2018-04-28 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 19:54 bug#31274: 27.0.50; xdisp.c:7575: Emacs fatal error: assertion failed: IT_BYTEPOS (*it) == CHAR_TO_BYTE (IT_CHARPOS (*it)) Stefan Monnier
2018-04-28 9:29 ` Eli Zaretskii [this message]
2018-04-28 9:47 ` Eli Zaretskii
2018-05-04 10:35 ` Noam Postavsky
2018-05-04 12:50 ` Eli Zaretskii
2019-09-26 19:29 ` 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=83h8nvu19w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31274@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).