I want to see how struct task_struct is defined, so I type cscope f g
task_struct. Here's the result.:
0 mmc_queue.h 5 struct task_struct;
1 cpu_buffer.h 18 struct task_struct;
2 udfdecl.h 42 struct task_struct;
3 current.h 6 struct task_struct;
4 processor.h 492 struct task_struct;
5 ptrace.h 58 struct task_struct;
6 system.h 12 struct task_struct;
7 file.h 79 struct task_struct;
8 profile.h 36 struct task_struct;
9 sched.h 528 struct task_struct {
a avc.h 32 struct task_struct;
As you can see, all except option 9 is helpful. I just wonder whether it can
be configured so that I don't see other options.
2011/1/27 Hans-Bernhard Bröker <HBBroeker@...>
> On 26.01.2011 16:40, Cyker Way wrote:
>
> A little inconvenience when I use cscope to browse code is that, I don't
>> know how to filter out declarations from definitions. Suppose I want to
>> find
>> how struct task_struct is defined, I use cscope f g task_struct, but the
>> declarations will also appear,
>>
>
> The declarations of what are those?
>
> Generally speaking, there is hardly ever a need for such thing as a
> declaration of a struct. In some self-referential data structures there are
> forward declarations of structs inside the structs themselves, but that's
> about it.
>
> Maybe you should give an actual example of what gets found when you don't
> want it to.
>
>
--
Cyker Way
Email:cykerway@... <Email%3Acykerway@...>
|