The JS engine uses the jsprobes.h interface to inject probes that may be handled by a variety of backends -- dtrace, ETW, callbacks, etc. For many analyses, it would be very helpful to have probes in the rest of the tree, so that we could eg diagnose event latencies by looking at what the JS engine did during the event's processing. I'm not sure if the current jsprobes "API" is right for this (it requires each probe to be individually named and possibly handled specifically for each relevant backend), and it definitely isn't intended to be #included around the tree. But there should be some way of injecting probes elsewhere in the tree and feeding them through to the same set of backends. I'll update the component once I figure out where this should live.
You need to log in before you can comment on or make changes to this bug.