Using SlowCalls: Difference between revisions

Jump to navigation Jump to search
m
(Created page with "== Getting a tree with instrumentation == First, you need to get a tree containing Javascript instrumentation that is fully working. ({{bug|507012}} added the instrumentation, b...")
 
Line 3: Line 3:
First, you need to get a tree containing Javascript instrumentation that is fully working. ({{bug|507012}} added the instrumentation, but it keeps getting perturbed by JS engine changes, so that it ends up getting mismatched JS function enters/exits.)
First, you need to get a tree containing Javascript instrumentation that is fully working. ({{bug|507012}} added the instrumentation, but it keeps getting perturbed by JS engine changes, so that it ends up getting mismatched JS function enters/exits.)


Option 1: mozilla-central
=== Option 1: mozilla-central ===


The current (2010-Oct-11) m-c tree's JS interpreter is in an intermediate state that I can't get the instrumentation working for. So my current workaround is to do a wholesale update to a fairly recent tracemonkey and then add some patches that fix the instrumentation there.
The current (2010-Oct-11) m-c tree's JS interpreter is in an intermediate state that I can't get the instrumentation working for. So my current workaround is to do a wholesale update to a fairly recent tracemonkey and then add some patches that fix the instrumentation there.
Line 15: Line 15:
That first patch is likely to rot rather quickly. If so, you could clone revision 19b462ec16a0 and copy out the js/src subtree from there instead.
That first patch is likely to rot rather quickly. If so, you could clone revision 19b462ec16a0 and copy out the js/src subtree from there instead.


Option 2: tracemonkey
=== Option 2: tracemonkey ===


The patches in {{bug|602067}} will get to the same state as the patched mozilla-central tree, above, but dvander has rewritten the JS engine integration in {{bug|603044}} to be much, much nicer. None of my patches will be needed after this lands. But I haven't tried it yet.
The patches in {{bug|602067}} will get to the same state as the patched mozilla-central tree, above, but dvander has rewritten the JS engine integration in {{bug|603044}} to be much, much nicer. None of my patches will be needed after this lands. But I haven't tried it yet.
Confirmed users
329

edits

Navigation menu