I would suggest instrumenting the resultant app.c file that the nesC compiler produces rather than each component itself during the compilation process. You can use the xml wiring file in conjunction with the app.c file to figure out the names of the commands and events you would like to instrument. Then you can just insert your code directly into the app.c file.
John Regehr from the University of Utah might be a good person to contact. He did something similar during his development of TinyOS contracts. http://sing.stanford.edu/pubs/spots07.pdf Kevin On 9/21/07, Jacob Sorber <[EMAIL PROTECTED]> wrote: > I'm interested in intercepting calls to an arbitrary TinyOS module in order > to instrument existing code for different types of dynamic analysis. I know > how to extract the NesC wiring graph using the -fnesc-dump options, but does > anyone know if there is a simple way to intercept edges in the graph using > the compiler tools? I can always modify the compiler to do my bidding, but > I would rather not. > > Any help would be much appreciated. Thanks, > > Jacob Sorber > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- ~Kevin _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
