On Fri, 31 Oct 2003, Eli Billauer wrote: > So I wrote a little utility, which scans through a project, and maps > which function calls which. It generates reports that tell you in which > file and line number each function is declared, who calls it, and who it > calls.
how is cdepend different from the existing cross-reference tools? why did you find the need to read debug information from binaries, instead of using some tool that parses the source (e.g. finding an existing lex+yacc based tool that already parses the C code, and adding your own parts in it? what is (are?) the advantage(s?) of parsing the binary file? as for questions about the tool itself: 1. does it handle static functions? those can appear in several source files, with the same name, and if all placed into the same directory, will result a collision. 2. i guess you didn't yet handle sources scattered on several directories - of you just presume someone will feed _all_ the '.S' files together, and you'll generate one gigantic directory for _all_ the functions in the code? 3. i presume you cannot handle function pointers passed around the code? that is, a pointer to function C is passed from function A to function B, and then function B be invokes this pointer - you won't be able to say that function B calls function C - would you? -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy -------------------------------------------------------------------------- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
