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>, 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 04:43:25 +0300	[thread overview]
Message-ID: <cb150c3f-6190-e95c-dac3-35de7ae4c892@yandex.ru> (raw)
In-Reply-To: <87367q1c9d.fsf@no.workgroup>

On 24.05.2020 02:07, Gregor Zattler wrote:
> This also happens with the binary from debian buster 10.4 ,
> therefore I don't think it is caused by my specific build
> options, which anyway are:
> 
> CFLAGS='-g -O2 -fdebug-prefix-map=/home/grfz/src/emacs=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-pie'
> 
> LDFLAGS='-Wl,-z,relro -no-pie'
> 
> CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2  '
> 
> ./configure -C --prefix=/usr/local/stow/emacs-snapshot --with-file-notification=inotify --with-cairo --without-toolkit-scroll-bars --with-x-toolkit=gtk3 --with-sound=yes --without-gconf --with-mailutils --with-x=yes --enable-checking=yes --enable-check-lisp-object-type=yes --with-nativecomp
> 
> 
> For me this assertion error is not a big problem since I now
> exclude the linux src tree from the tags creation because of
> emacs performance reasons.

Thanks you for that addition.

Indeed, when I configure Emacs with

   CFLAGS='-g -O2' --enable-checking

etags does abort with assertion errors you described.





  reply	other threads:[~2020-05-24  1:43 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 [this message]
     [not found]           ` <87r1v9hl9s.fsf@no.workgroup>
2020-05-24 14:18             ` Dmitry Gutov
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=cb150c3f-6190-e95c-dac3-35de7ae4c892@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).