From: Dan Carpenter <error27@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [0/4] inspector for sparse
Date: Fri, 23 Apr 2010 22:37:51 +0200 [thread overview]
Message-ID: <20100423203751.GM29093@bicker> (raw)
In-Reply-To: <20100423203040.GL29093@bicker>
On Fri, Apr 23, 2010 at 10:30:40PM +0200, Dan Carpenter wrote:
> On Fri, Apr 02, 2010 at 11:59:39AM -0700, Christopher Li wrote:
> > I add a treeview branch on sparse/chrisl so you can pull from it.
> >
> > http://git.kernel.org/?p=devel/sparse/chrisl/sparse.git;a=shortlog;h=refs/heads/treeview
> >
> > In fedora, you need to install gtk2-devel package to enable it.
> >
> > Chris
>
> This is an really useful program.
>
> Inline functions don't show up in the list of functions. Is there a way
> to inspect these as well? This is more a general sparse question, since
> smatch doesn't parse inline functions either.
Crap. I'm dumb. You actually can click through your program to where the
inline function is called and see it.
Really useful program as I said before.
regards,
dan carpenter
>
> regards,
> dan carpenter
next prev parent reply other threads:[~2010-04-23 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 18:36 [0/4] inspector for sparse Christopher Li
2010-04-02 18:59 ` Christopher Li
2010-04-23 20:30 ` Dan Carpenter
2010-04-23 20:37 ` Dan Carpenter [this message]
2010-04-25 8:37 ` 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=20100423203751.GM29093@bicker \
--to=error27@gmail.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 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.