all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: 41465@debbugs.gnu.org
Subject: bug#41465: 28.0.50 (but also earlier versions); etags asserion error (with too many files?)
Date: Fri, 22 May 2020 21:31:57 +0200	[thread overview]
Message-ID: <87sgfr936a.fsf@no.workgroup> (raw)

Dear emacs developers,

I get an assertion error when executing the following line
(from a cron job of mine):

grfz@no:~/src$ find ~/src -type f -print0 | egrep -zZ '(\.el|\.c|\.h)(\.gz)?$' | xargs -0r etags
etags: etags.c:1987: pfnote: Assertion `name == NULL || name[0] != '\0'' failed.
xargs: etags: terminated by signal 6
125 (master *) grfz@no:~/src$

This happens with etags from debian buster, as with etags
build from emacs-27 branch of emacs git repo, as with etags build
from feature/native-comp branch.


Under ~/src there is also the linux kernel git repo.  There
is no assertion error if I filter it out:

$ find . -type f -print0 | egrep -vzZ linux | egrep -zZ '(\.el|\.c|\.h)(\.gz)?$' | xargs -0r etags
0 (master *) grfz@no:~/src$

There is also no assertion error if I filter for .el files
only:

125 (master *) grfz@no:~/src$ find ~/src -type f -print0 | egrep -zZ '(\.el)(\.gz)?$' | xargs -0r etags
0 (master *) grfz@no:~/src$


Therefore I assume this somehow is related to the number of files.


Ciao; Gregor
--
 -... --- .-. . -.. ..--.. ...-.-






             reply	other threads:[~2020-05-22 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 19:31 Gregor Zattler [this message]
2020-05-22 21:38 ` bug#41465: 28.0.50 (but also earlier versions); etags asserion error (with too many files?) 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
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

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

  git send-email \
    --in-reply-to=87sgfr936a.fsf@no.workgroup \
    --to=telegraph@gmx.net \
    --cc=41465@debbugs.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.