Re: Help analyzing the parsed paths to help reduce the GTAGS size

[Kaushal Modi]

Thank you! That helps me tremendously.

--
Kaushal Modi

On Thu, May 19, 2022 at 3:00 AM Shigio YAMAGUCHI <shigio@gnu.org> wrote:
>
> Hello,
> You can use the -d option to dump a tag file.
>
>         $ gtags -d GPATH
>         $ gtags -d GTAGS
>
> Regards,
> Shigio
>
> On Thu, May 19, 2022 at 5:34 AM Kaushal Modi <kaushal.modi@gmail.com> wrote:
> >
> > Hello,
> >
> > I am using GNU Global to parse a huge project, but the GTAGS file
> > seems to get much larger than I expect. This file used to be around
> > 5GB but after some updates in the project this file has blown up in
> > size.
> >
> > .rw-r--r--   16G kmodi 17 May 19:18 GTAGS
> > .rw-r--r--   14M kmodi 17 May 19:18 GPATH
> > .rw-r--r--  7.9M kmodi 17 May 19:18 GRTAGS
> >
> > Is there a good way to diagnose which paths in the project contribute
> > to this? Often, gtags crawl into certain paths which I don't typically
> > care.
> >
> > If I can get visibility into which paths were parsed, that can help me
> > reduce the db size too. For example, is there a way to print the GPATH
> > in plain ascii format?
> >
> > Thanks!
> >
> > --
> > Kaushal Modi
> >
>
>
> --
> Shigio YAMAGUCHI <shigio@gnu.org>
> PGP fingerprint:
> 26F6 31B4 3D62 4A92 7E6F  1C33 969C 3BE3 89DD A6EB