all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Werner LEMBERG <wl@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: intervals.c:1190: Emacs fatal error: assertion failed: amt == 0
Date: Sat, 04 Apr 2020 12:57:57 +0300	[thread overview]
Message-ID: <83k12vvahm.fsf@gnu.org> (raw)
In-Reply-To: <20200403.152721.1413216816446827763.wl@gnu.org> (message from Werner LEMBERG on Fri, 03 Apr 2020 15:27:21 +0200 (CEST))

> Date: Fri, 03 Apr 2020 15:27:21 +0200 (CEST)
> Cc: emacs-devel@gnu.org
> From: Werner LEMBERG <wl@gnu.org>
> 
> > Thanks.  Any hope of having a reproducible recipe that doesn't
> > involve that particular message and/or mew?
> 
> Alas, no.  I'm willing to help with further analysis if you tell me
> what to do.
> 
> I'm attaching the problematic e-mail; however, I decoded it with
> 'munpack -t' and also with a small perl script to get the header lines
> in standard UTF8, and Emacs was able to read this data just fine.
> 
> For bisecting the issue, what date or commit do you suggest as the
> starting point for testing?
> 
> > Alternatively, does reverting
> > dc3006cf1419e5b22c35fa36d79ba029d0482df1 make this problem go away?
> 
> No, it doesn't.

How about 31182c1d17f6f7bc946d5e4576e025c9b975e0b5?

If that doesn't help, either, I guess start from the branch point of
emacs-27, and if that version also exhibits the problem, try Emacs
26.3.

Thanks.



  reply	other threads:[~2020-04-04  9:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 11:02 intervals.c:1190: Emacs fatal error: assertion failed: amt == 0 Werner LEMBERG
2020-04-03 12:41 ` Eli Zaretskii
2020-04-03 13:27   ` Werner LEMBERG
2020-04-04  9:57     ` Eli Zaretskii [this message]
2020-04-04 10:16       ` Werner LEMBERG
2020-04-04 11:23         ` Eli Zaretskii
2020-04-04 20:56       ` Werner LEMBERG
2020-04-05  2:30         ` Eli Zaretskii
2020-04-05  5:42           ` Werner LEMBERG
2020-04-05 13:07             ` Eli Zaretskii
2020-04-06  6:36               ` Werner LEMBERG
2020-04-06 13:24                 ` Eli Zaretskii
2020-04-09  8:24                   ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k12vvahm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=wl@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.