From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: larsi@gnus.org, 45246@debbugs.gnu.org, grfz@gmx.de
Subject: bug#45246: 28.0.50; etags assertion error
Date: Tue, 07 Jun 2022 20:15:10 +0300 [thread overview]
Message-ID: <83wnds5ra9.fsf@gnu.org> (raw)
In-Reply-To: <87bkv42zu1.fsf@igel.home> (message from Andreas Schwab on Tue, 07 Jun 2022 18:38:46 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Gregor Zattler <grfz@gmx.de>, larsi@gnus.org, 45246@debbugs.gnu.org
> Date: Tue, 07 Jun 2022 18:38:46 +0200
>
> On Jun 07 2022, Eli Zaretskii wrote:
>
> > Lars, I guess you were trying this in an optimized build, where all
> > the assertions compile to nothing.
>
> It's not about optimized or not, it's controlled by --enable-checking.
In etags.c? I see no ENABLE_CHECKING there. I do see
#include <assert.h>
next prev parent reply other threads:[~2022-06-07 17:15 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
2022-06-07 16:38 ` Andreas Schwab
2022-06-07 17:15 ` Eli Zaretskii [this message]
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
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=83wnds5ra9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45246@debbugs.gnu.org \
--cc=grfz@gmx.de \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.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).