[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#45246: 28.0.50; etags assertion error
From: |
Eli Zaretskii |
Subject: |
bug#45246: 28.0.50; etags assertion error |
Date: |
Fri, 10 Jun 2022 10:25:52 +0300 |
> From: Gregor Zattler <grfz@gmx.de>
> Cc: 45246@debbugs.gnu.org
> Date: Fri, 10 Jun 2022 00:33:07 +0200
>
> >> > And indeed, invoking "etags -I" compiled with --enable-checking with
> >> > the original file avoids the assertion violation. And in a production
> >> > build, etags produces a valid TAGS file even if -I is omitted.
> >> >
> >> > So I think there's nothing to do here, and we should close this bug as
> >> > notabug. Does anyone disagree?
> >>
> >> I think that sounds correct.
>
> I confirm -I avoids the assertion.
>
> > Gregor, any objections to closing this bug?
>
> no.
OK, done.
> I must admit, I did not read the man pager closely but
> anyway I wouldn't have understood the consequences of
> setting vs not setting -I. Perhaps the documentation could
> be amended somehow?
I've added some notes about this to the manual and to the etags man
page, thanks.
> I assume this is a trade-of between speed and robustness?
No, I think it's more about the correctness of the produced TAGS file
than about speed. etags's C/C++ parser is extremely naïve and largely
ignores the complicated syntax of the C dialects. So using the
"closing brace in column zero ends all top-level definitions"
heuristic is useful for preventing 'etags' from being utterly confused
by some sophisticated use of C/C++ facilities, such as macros and the
more arcane syntactic constructs in modern C++: it makes sure the
confusion ends as early as possible.
> I do not have objections to closing this bug
> report, but I wonder why etags treats closing braces in
> the first column special if it does not speed up things?
See above. Whether this is a real problem, I don't know. I think
the only way to tell is to try. At least with our test suite for
'etags', using -I causes regressions, e.g. in cp-src/c.C some tags are
not created. So I think having this heuristic on by default is a good
thing, overall.
- bug#45246: 28.0.50; etags assertion error, (continued)
- bug#45246: 28.0.50; etags assertion error, Eli Zaretskii, 2022/06/07
- bug#45246: 28.0.50; etags assertion error, Eli Zaretskii, 2022/06/09
- bug#45246: 28.0.50; etags assertion error, Lars Ingebrigtsen, 2022/06/09
- bug#45246: 28.0.50; etags assertion error, Eli Zaretskii, 2022/06/09
- bug#45246: 28.0.50; etags assertion error, Gregor Zattler, 2022/06/09
- bug#45246: 28.0.50; etags assertion error,
Eli Zaretskii <=
- bug#45246: 28.0.50; etags assertion error, Eli Zaretskii, 2022/06/10
- bug#45246: 28.0.50; etags assertion error, Francesco Potortì, 2022/06/10
- bug#45246: 28.0.50; etags assertion error, Lars Ingebrigtsen, 2022/06/07