From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Carl Spalletta <cspalletta@yahoo.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Interesting failures of 'cscope'
Date: Wed, 04 Aug 2004 16:39:04 -0700 [thread overview]
Message-ID: <237280000.1091662744@flay> (raw)
In-Reply-To: <20040804232252.30644.qmail@web53802.mail.yahoo.com>
Various versions of cscope are buggy as hell, and I'm not at all sure the
recent ones are any better than older ones ... caveat user ;-)
Personally I use an old binary ripped off RH 6.2, which still seems to
work ... any current ones I've tried are broken.
M.
--On Wednesday, August 04, 2004 16:22:52 -0700 Carl Spalletta <cspalletta@yahoo.com> wrote:
> FYI
>
> The first failure seems to be a confusion between function declarations and definitions -
> eg for linux-2.6.7, it says FsmNew() is called by drivers/isdn/hisax/fsm.h::CallcNew, thus:
>
> $cscope -d -p9 -L -3 FsmNew
> ...
> drivers/isdn/hisax/fsm.h CallcNew 50 int FsmNew(struct Fsm *fsm, struct FsmNode,*fnlist, int
> fncount);
> ...
>
> but there is no call there, only an external declaration of FsmNew, and no declaration of
> CallcNew of any kind whatsoever in that file!
>
>
> The second failure appears to be related to an inability to cope with complicated declarations
> within a prototype, such of those of type pointer-to-function. For example, the definition:
>
> struct net_device *alloc_netdev(int sizeof_priv, const char *mask,
> void (*setup)(struct net_device *))
>
> from line 73 of drivers/net/net_init.c, is not recognized by cscope as a valid function definition
> and so it does not find the call to kmalloc (or anything else) contained in that function.
>
> $ cscope -d -p9 -L -1 alloc_netdev
> <nothing>
> $ cscope -d -p9 -L -3 kmalloc | grep alloc_netdev
> <nothing>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2004-08-04 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 23:22 Interesting failures of 'cscope' Carl Spalletta
2004-08-04 23:39 ` Martin J. Bligh [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-04 23:37 Carl Spalletta
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=237280000.1091662744@flay \
--to=mbligh@aracnet.com \
--cc=cspalletta@yahoo.com \
--cc=linux-kernel@vger.kernel.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.