yeah I did all that. Perhaps I don't know where to look but it pretty much looks like noise to me.
On Mon, Mar 22, 2010 at 7:48 PM, Kevin Klues <[email protected]> wrote: > Also, make sure you have the following configuration parameters set: > > EXTRACT_ALL = YES > HAVE_DOT = YES > > and that graphviz is installed. > > Kevin > > On Mon, Mar 22, 2010 at 7:16 PM, Kevin Klues <[email protected]> wrote: > > That's exactly what doxygen should give you if you enable those > > configuration parameters. There might be some more though. I've > > attached a configuration file that I'm using for another project, and > > it definitely has the clickable call graphs stuff working for both > > forward and reverse directions. > > > > Kevin > > > > On Mon, Mar 22, 2010 at 7:05 PM, Eric Decker <[email protected]> wrote: > >> I went ahead and tried using doxygen on the app.c but haven't been able > to > >> get anything meaningful out of it. I did configure CALL_GRAPH and > >> CALLER_GRAPH. But haven't found any output that makes sense to me. > >> What I really want is a call graph and a caller graph showing the wiring > >> graph akin to what nesdoc provides. But all together in a way I can > >> traverse easily. > >> any thoughts? > >> eric > >> > >> On Mon, Mar 22, 2010 at 5:33 PM, Kevin Klues <[email protected]> wrote: > >>> > >>> You could just run doxygen on the resulting app.c file. There are > >>> configuration parameters that let you generate both forward and > >>> reverse call graphs from. > >>> > >>> Kevin > >>> > >>> On Mon, Mar 22, 2010 at 4:12 PM, Eric Decker <[email protected]> > wrote: > >>> > I know about nesdoc (built via make <platform> docs). And I need > >>> > something > >>> > a bit different. > >>> > I'm interested in a full call graph. Not the pieces that nesdoc > gives > >>> > you. > >>> > Also interested in a reverse call graph (what calls). > >>> > For example I trying to analyze the resource usage of various > devices. > >>> > Who > >>> > is using what device. > >>> > So I'd like to answer the question who wires into HplMsp430UsciB1C > >>> > (msp430X > >>> > h/w). But I'm > >>> > not that interested in the first level wiring but rather where does > the > >>> > call > >>> > graph start and who is > >>> > wired in along the way. > >>> > It helps answer the question of who is wired into this device when > >>> > things > >>> > are screwy for a complex > >>> > system. > >>> > Anyone done something like this? > >>> > -- > >>> > Eric B. Decker > >>> > Senior (over 50 :-) Researcher > >>> > > >>> > > >>> > > >>> > _______________________________________________ > >>> > Tinyos-help mailing list > >>> > [email protected] > >>> > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > >>> > > >>> > >>> > >>> > >>> -- > >>> ~Kevin > >> > >> > >> > >> -- > >> Eric B. Decker > >> Senior (over 50 :-) Researcher > >> > >> > >> > > > > > > > > -- > > ~Kevin > > > > > > -- > ~Kevin > -- Eric B. Decker Senior (over 50 :-) Researcher
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
