unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Gregor Zattler <telegraph@gmx.net>
Cc: 41465@debbugs.gnu.org
Subject: bug#41465: 28.0.50 (but also earlier versions); etags asserion error (with too many files?)
Date: Sun, 24 May 2020 17:18:07 +0300	[thread overview]
Message-ID: <5d285545-e4fe-f9bb-813f-2d2bb83a7b2d@yandex.ru> (raw)
In-Reply-To: <87r1v9hl9s.fsf@no.workgroup>

Hi Gregor,

Please keep the bug email in Cc.

On 24.05.2020 09:58, Gregor Zattler wrote:
> Hi Dmitry,
> * Dmitry Gutov <dgutov@yandex.ru> [2020-05-24; 04:43]:
>> Thanks you for that addition.
>>
>> Indeed, when I configure Emacs with
>>
>>     CFLAGS='-g -O2' --enable-checking
>>
>> etags does abort with assertion errors you described.
> 
> arghs, my statement "also happens with the binary from
> debian buster 10.4" was wrong.  I tested with /usr/bin/etags
> but forgot I that wrestled my emacs-27 build into the
> alternatives system of debian.
> 
> I tested again with
> 
> 0 (master *) grfz@no:~$ /usr/bin/etags.emacs ~/src/linux//include/net/mac80211.h
> 0 (master *) grfz@no:~$ /usr/bin/etags.emacs ~/src/linux/sound/soc/codecs/cs43130.c
> 
> and now there are no assertion errors with these files.

Makes sense.

> But shouldn't there also be no assertion errors with
> --enable-checking ?

There shouldn't be.

So it's a valuable bug report, just less urgent than we might have 
decided previously.

I'll let our developers who know etags better handle it from here.





  parent reply	other threads:[~2020-05-24 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 19:31 bug#41465: 28.0.50 (but also earlier versions); etags asserion error (with too many files?) Gregor Zattler
2020-05-22 21:38 ` Dmitry Gutov
     [not found]   ` <87pnavt5h4.fsf@no.workgroup>
2020-05-23 20:22     ` Dmitry Gutov
2020-05-23 23:07       ` Gregor Zattler
2020-05-24  1:43         ` Dmitry Gutov
     [not found]           ` <87r1v9hl9s.fsf@no.workgroup>
2020-05-24 14:18             ` Dmitry Gutov [this message]
2020-05-24 15:04           ` 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

  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=5d285545-e4fe-f9bb-813f-2d2bb83a7b2d@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=41465@debbugs.gnu.org \
    --cc=telegraph@gmx.net \
    /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).