Difference between revisions of "Add DTrace Probes and scripts for Mozilla Code base"
Hellwolf36 (talk | contribs) (→Project News) |
Hellwolf36 (talk | contribs) (→Project Details) |
||
| Line 33: | Line 33: | ||
Objective 1) Get in contact with people behind the project (0 %) <br \> | Objective 1) Get in contact with people behind the project (0 %) <br \> | ||
| − | Objective 2) Learn how to write Probing programs in D ( | + | Objective 2) Learn how to write Probing programs in D (Done 10/14/08) <br \> |
Objective 3) Specify 0.1 release (Done 10/05/08) <br \> | Objective 3) Specify 0.1 release (Done 10/05/08) <br \> | ||
Objective 4) Compile Mozilla Firefox on Mac PC for D-Trace functionality (Done 10/09/08) <br \> | Objective 4) Compile Mozilla Firefox on Mac PC for D-Trace functionality (Done 10/09/08) <br \> | ||
Revision as of 14:35, 14 October 2008
Contents
Project Name
Add DTrace Probes and scripts for Mozilla Code base
Project Description
DTrace was created by Sun in OpenSolaris to allow developers to write simple scripts in order to probe and instrument executing programs in a way not possible otherwise. One of the advantages of DTrace is that it allows you to turn on probing when you need it, but not incur an execution penalty with regard to performance (i.e., when probes aren't being scripted, they aren't run). This requires developers to add "probes" to their source code. For example, if you wanted to know when a particular function is entered/exited, get info about what happened, etc. you could add probes to the particular function. Writing the probes is not difficult, however there are hundreds or thousands of probes that Mozilla would like across its code base.
Resources: sayrer
0.1 Release
I am looking at 2 major things for this release.
1) Either create a simple D-Trace program or use an existing one and pick up on function calls within a certian aspect of the Mozilla Code Base
2) Make sure that Mozilla Firefox runs on Mac, and the D-Trace script doesnt crash Mac and/or Firefox.
For code submission, I will be submitting the D script I used (if I made it) or the location of the D script used (if I used an existing one). And a message.log file with the output of the script.
Project Leader(s)
Project Contributor(s)
When I reach the stage where my Probe programs work, I may lend my functionality to other users to see if it works on seperate parts than the areas I am working on. For instance, I can lend the probing technology to a person working on Songbird, or Thunderbird.
Contact me on IRC - nick is Hellwolf_36 if interested. I will be coming online mostly everyday starting Tuesday.
Project Details
Objective 1) Get in contact with people behind the project (0 %)
Objective 2) Learn how to write Probing programs in D (Done 10/14/08)
Objective 3) Specify 0.1 release (Done 10/05/08)
Objective 4) Compile Mozilla Firefox on Mac PC for D-Trace functionality (Done 10/09/08)
Objective 5) Complete the requirements for 0.1 (50 %)
Project News
09/19/08
- Created this status page.
10/05/08
- Added 0.1 spec (was busy) - Started working on Probing software on C++
10/09/08
- Compiled Mozilla Firefox on Mac with D-Trace option sucessfully - Began reading resources for D-Trace programming.
10/12/08
-Remodified 0.1 spec based on discussion with David Humphrey
10/14/08
- Created the D Script that will do the function call counting - Installed a patch that will allow my D Script to work - Recompiled Mozilla Firefox on Mac to save patch
