From: Alan Mackenzie <acm@muc.de>
To: Glenn Morris <rgm@gnu.org>
Cc: 28280@debbugs.gnu.org
Subject: bug#28280: Maximally unhelpful diagnostic message.
Date: Tue, 29 Aug 2017 20:15:57 +0000 [thread overview]
Message-ID: <20170829201557.GB4339@ACM> (raw)
In-Reply-To: <fmh8wqdvuw.fsf@fencepost.gnu.org>
Hello, Glenn.
On Tue, Aug 29, 2017 at 15:20:23 -0400, Glenn Morris wrote:
> Alan Mackenzie wrote:
> > Assertion failed: (eq 10 (char-before))
> A few seconds grep suggests this is due to the code in newline, added ~
> 3 years ago in 62ee8b1 ("Add assertions to try and help catch bug#18913").
> The complete lack of progress in that report since then suggests it may
> be time to remove/downgrade those assertions.
Yes, but that's a separate problem from the essence of the bug report.
Regardless of the lack of progress on bug #18913, the information
provided by an assert being triggered is unhelpful and inadequate.
That aside, I can't see how the two assertions suggested in #18913 could
trigger the message I saw. I'll maybe have a look at the actual patch
sometime when I'm less tired.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-08-29 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 18:41 bug#28280: Maximally unhelpful diagnostic message Alan Mackenzie
2017-08-29 19:20 ` Glenn Morris
2017-08-29 19:32 ` John Wiegley
2017-08-29 20:15 ` Alan Mackenzie [this message]
2017-08-30 12:17 ` npostavs
2020-08-24 13:59 ` Lars Ingebrigtsen
2020-10-11 2:08 ` Lars Ingebrigtsen
2017-08-30 19:51 ` Glenn Morris
2017-08-31 21:11 ` Alan Mackenzie
2017-09-18 5:35 ` Paul Eggert
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=20170829201557.GB4339@ACM \
--to=acm@muc.de \
--cc=28280@debbugs.gnu.org \
--cc=rgm@gnu.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).