esp. with #1, we're going to need some framework for managing dtrace probes easier. random thoughts:
[x] most dispatch on the record-side signal handler is based on the probe name. is there a nice way we could have the interface for this dtrace lib be something like "register this probe point, and use this callback func to create an Option\<Recordable> when it's hit", moving the dispatch into the dtrace instance?
[ ] for #1 this is also going to need to support retrying probe registration after a dyld notification
esp. with #1, we're going to need some framework for managing dtrace probes easier. random thoughts: