Arvid Norlander
Arvid Norlander
Yes, that worked in the end (discovered a few weeks ago, but forgot to update this bug report). Perhaps the documentation should be a bit better though, especially for people...
> One way to tell if you need to use DSOs if that if your plugins share memory with each other or with some "main" program or with other shared...
> In the emscripten model the main module includes libc and the side module(s) import all the libc symbols from the main module: https://emscripten.org/docs/compiling/Dynamic-Linking.html Reading this, it doesn't look like...
Still not merged? Is this waiting for anything else?
> Are you attaching to a running process or starting the process directly from samply? The former is currently implemented in a less efficient way, and could potentially cause issues....
I don't believe it is cargo-bininstall. It seems to apply to all packages I build via "cargo install-update" as opposed to "cargo install". Cargo-bininstall was just the example I pasted...
Oh, didn't know that. I can try when I get back to the office. Right now it is hard to try: 1) everything is up-to-date 2) I'm working remotely today...
Thanks I will check it out today when I'm at the office.
I had nothing that needed updating, but `cargo auditable install-update -f cargo-about` worked and was able to use cargo-binstall with the new version, so I suspect this is working properly...