Implement dtrace log parsing for MacOSX.

Implement dtrace log parsing for MacOSX.

Rename strace_inputs.py to trace_inputs.py since it's now using both strace and
dtrace, depending on the platform.

R=rogerta@chromium.org
BUG=98636
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=127100

[M-A Ruel, 2012-03-15 15:16:22]

Still works on both mac and linux. Helps a lot in finding the current
dependencies.

It was important to get it working on mac because it has significantly different
dependencies, especially for resources.

[Roger Tawa OOO till Jul 10th, 2012-03-15 18:07:16]

lgtm

A couple of question about dtrace code, but likely my misunderstanding.

http://codereview.chromium.org/9706058/diff/1/tools/isolate/trace_inputs.py
File tools/isolate/trace_inputs.py (right):

http://codereview.chromium.org/9706058/diff/1/tools/isolate/trace_inputs.py#n...
tools/isolate/trace_inputs.py:123: dtrace:::BEGIN {
triple ::: ?  is that correct?  same at line 134.

http://codereview.chromium.org/9706058/diff/1/tools/isolate/trace_inputs.py#n...
tools/isolate/trace_inputs.py:135: trackedpid[pid] = 1;
should you be using ppid here?

[M-A Ruel, 2012-03-15 18:09:54]

http://codereview.chromium.org/9706058/diff/1/tools/isolate/trace_inputs.py
File tools/isolate/trace_inputs.py (right):

http://codereview.chromium.org/9706058/diff/1/tools/isolate/trace_inputs.py#n...
tools/isolate/trace_inputs.py:123: dtrace:::BEGIN {
On 2012/03/15 18:07:16, Roger Tawa wrote:
> triple ::: ?  is that correct?  same at line 134.

Yep, that's how it works.

http://codereview.chromium.org/9706058/diff/1/tools/isolate/trace_inputs.py#n...
tools/isolate/trace_inputs.py:135: trackedpid[pid] = 1;
On 2012/03/15 18:07:16, Roger Tawa wrote:
> should you be using ppid here?

No. What it is doing is: if the parent's process is traced (line 134), all its
children are traced too (line 135).

[commit-bot: I haz the power, 2012-03-15 18:23:13]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/maruel@chromium.org/9706058/1

[commit-bot: I haz the power, 2012-03-15 22:44:19]

Try job failure for 9706058-1 (retry) on win_rel for step "browser_tests".
It's a second try, previously, steps "ui_tests, browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2012-03-16 00:01:58]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/maruel@chromium.org/9706058/1

[commit-bot: I haz the power, 2012-03-16 04:18:27]

Change committed as 127100