linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josht@linux.vnet.ibm.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org,
	Aneesh Kumar <aneesh.kumar@gmail.com>,
	dhaval@linux.vnet.ibm.com
Subject: Re: sparse ctags
Date: Mon, 06 Aug 2007 12:03:07 -0700	[thread overview]
Message-ID: <1186426987.3089.27.camel@josh-work.beaverton.ibm.com> (raw)
In-Reply-To: <cc723f590706260145q708c4390kf5b6ccbaf84000ef@mail.gmail.com>

On Tue, 2007-06-26 at 14:15 +0530, Aneesh Kumar wrote:
> Is there a document how to use this ? Does this work on multiple files
> ? Looking at the source i see it opening tags in truncate mode

No documentation, unfortunately.  The Sparse ctags doesn't take any
options.  It should work on multiple files by simply giving all the
files on one ctags command line, with something like:
ctags $(find -name '*.c')

However, it seems to have some problems at the moment running on even
*one* file:

$ ./ctags ctags.c
unknown symbol const namespace:2 type:17

$ ./ctags validation/context.c
unknown symbol const namespace:2 type:17

type 17 refers to SYM_KEYWORD, which seems consistent with "unknown
symbol const", though I don't know why ctags would look at const as a
symbol.

I've CCed Christopher Li, the author of the Sparse ctags implementation.
Chris, can you look into this problem and suggest a possible solution?

- Josh Triplett

  reply	other threads:[~2007-08-06 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-26  8:45 sparse ctags Aneesh Kumar
2007-08-06 19:03 ` Josh Triplett [this message]
2007-08-07  3:38   ` Josh Triplett
2007-08-08  9:30     ` Christopher Li

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=1186426987.3089.27.camel@josh-work.beaverton.ibm.com \
    --to=josht@linux.vnet.ibm.com \
    --cc=aneesh.kumar@gmail.com \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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.
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 NNTP newsgroup(s).