Re: Add enable/disable methods

[Eric Wong <e@80x24.org>]

Sam Saffron <sam.saffron@gmail.com> wrote:
> Howdy,
> 
> In our use case we would like to profile one of N unicorn workers
> after a certain timeframe.
> 
> Would you be open to adding
> 
> `Mwrap.enable` : start profiling memory allocations
> `Mwrap.disable` : disable all profiling of memory allocations, making
> them as close as possible to a no-op.
> 
> and an env var for starting disabled
> 
> `MWRAP_OPTIONS=disabled`

Would still have to pay the extra size + tracking overhead
even in no-op mode; since post-enable free() can operate on
pre-enable malloc() results.

> 
> An additional convenience method here for the entire workflow would be:
> 
> `mwrap so_path` that returns the path to the module that needs
> preloading, this makes it slightly easier to configure production
> environments.
> 
> Thoughts?

Should be doable.  Got a bunch of other stuff coming up into the
weekend; but should be able to find some time for it in a week
or two.