On Mon, Nov 14, 2016 at 06:46:23PM +0000, Wookey wrote: > Package: global > Version: 5.7.1-2 > Severity: normal > > I have a built kernel tree for 3.16. > > running gtags on it gives a "directory stack over flow" error. > ~/debian/linux-3.16.7-ckt9$ gtags > gtags: directory stack over flow.
What are you actually building that source with? Because this: > Warning: symbolic link loop detected. > 'debian/build/source_none/debian/build/source_none/' is ignored. > Warning: symbolic link loop detected. > 'debian/build/source_none/debian/build/build_arm64_none_arm64/source/' is > ignored. > Warning: symbolic link loop detected. > 'debian/build/build_arm64_none_arm64/source/debian/build/source_none/' is > ignored. > Warning: symbolic link loop detected. > 'debian/build/build_arm64_none_arm64/source/debian/build/build_arm64_none_arm64/source/' Looks like a bug in your build scripts to be creating the symlink loops. I don't see anything like that in any of my kernel build trees ... Either way though, if you're actually seriously using this to index built kernel trees, then I'd recommend you look at the skip option for gtags configuration, to avoid having it uselessly crawl all over the build artifacts in the tree in any case, every time you run it to update the tags. And I assume that if you do that, it does index the kernel for you just fine? We could look at pulling the newer find code in if that's really a benefit to someone, but in this case, it looks like you've got a bug in your build scripts that other things will choke on too, and the easy 'fix' for that is something you probably ought to be doing on codebases this size anyway, if you're actually using it on them. Cheers, Ron
