all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gregor Zattler <grfz@gmx.de>
Cc: larsi@gnus.org, 45246@debbugs.gnu.org
Subject: bug#45246: 28.0.50; etags assertion error
Date: Tue, 07 Jun 2022 18:58:13 +0300	[thread overview]
Message-ID: <838rq879ey.fsf@gnu.org> (raw)
In-Reply-To: <87a6ao7dnh.fsf@no.workgroup> (message from Gregor Zattler on Tue, 07 Jun 2022 16:26:42 +0200)

> Cc: 45246@debbugs.gnu.org
> From: Gregor Zattler <grfz@gmx.de>
> Date: Tue, 07 Jun 2022 16:26:42 +0200
> 
> > on the supplied file, but I didn't see any assertion errors, either with
> > the etags from Emacs 28 or 29.
> >
> > Do you still see this problem in recent Emacs versions?
> 
> 
> Yes:
> 
> $ /home/grfz/src/emacs/lib-src/etags /usr/include/xapian/unicode.h
> etags: etags.c:4188: C_entries: Assertion `bracelev == typdefbracelev' failed.
> Aborted

Lars, I guess you were trying this in an optimized build, where all
the assertions compile to nothing.

I see this here and will try to take a look when I have time.





  reply	other threads:[~2022-06-07 15:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 23:38 bug#45246: 28.0.50; etags assertion error Gregor Zattler
2022-06-07 11:35 ` Lars Ingebrigtsen
2022-06-07 14:26   ` Gregor Zattler
2022-06-07 15:58     ` Eli Zaretskii [this message]
2022-06-07 16:38       ` Andreas Schwab
2022-06-07 17:15         ` Eli Zaretskii
2022-06-07 17:34           ` Andreas Schwab
2022-06-07 18:25             ` Eli Zaretskii
2022-06-07 17:08       ` Eli Zaretskii
2022-06-09 17:42         ` Eli Zaretskii
2022-06-09 18:43           ` Lars Ingebrigtsen
2022-06-09 18:59             ` Eli Zaretskii
2022-06-09 22:33               ` Gregor Zattler
2022-06-10  7:25                 ` Eli Zaretskii
2022-06-10  7:26                 ` Eli Zaretskii
2022-06-10 14:01                   ` Francesco Potortì
2022-06-07 17:13       ` 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

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

  git send-email \
    --in-reply-to=838rq879ey.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45246@debbugs.gnu.org \
    --cc=grfz@gmx.de \
    --cc=larsi@gnus.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.