Koute
Koute
This is expected and is not a bug. Commenting out [this line](https://github.com/koute/bytehound/blob/d0b19642d06821cd372903c201f32bfb65636f82/preload/src/global.rs#L556) will *probably* make it work.
Well, ideally it'd probably be the best to just have an env var to configure this behavior. You don't want it to follow fork by default since that would in...
> I can make a pr to add an env var. What is the format of existing env vars? https://github.com/koute/bytehound/blob/master/preload/src/opt.rs#L121
Okay, wait, by "child after `libc::fork`" did you actually mean "after `fork` + `exec`" (which what was I assumed), or do you *really* mean after `fork` *only*? It will indeed...
The whole internal state would have to be reset and essentially reinitialized: the queues and caches would have to be cleared, the global locks all forcibly recreated to make sure...
Is this on `master` or is this the `0.8.0` release?
Unless I hit this panic myself I have no plans to implement it. PRs are welcome though.
The yarn failure was due to a brainfart on my part where I accidentally forgot to commit the necessary file; it's fixed now. As far as this issue, unfortunately I...
Okay, I *think* it should be fixed now?
This is expected. Previously starting/stopping profiling would create a new file, but that's problematic for several reasons. The current behavior is that there's always only one file, and if you...