🚀 go-pugleaf

I'd like to restructure a large body of source code (and especially to
tidy up the includes).

Thus, I'd like to know more about the definitions and usages of things
in the source. I would prefer that this is not "name" based like cxref,
but that if there is a local variable "x", say, it's definition and uses
are distinguished from the definition and uses of a global variable "x".
I need to trace all things that can be defined and used - i.e
variables, macros, structs, unions, enums, typedefs.

It seems to me that instrumenting gcc would be a reasonable approach to 
generating such a database of information. Has anyone worked on this?

I don't much mind the format that the data is produced in - I can munge it
appropriately.

P.
-- 
Paul Hudson    paulh@harlequin.co.uk    +44 223 872522 (fax 872519)
Harlequin Ltd, Barrington Hall, Barrington, Cambs. CB2 5RG, England
"PaulhCo: registered nowhere, no liability at all President: paulh CEO: paulh
 Founders: paulh@hamjudo.mi.org, paulh@harlequin.com      VP Marketing: paulh"