Robert Gabriel Jakabosky

I tried defining `__cxa_thread_atexit` and `__cxa_thread_atexit_impl` in the guest, host, guest and host. Only defining it in the host (disabling TLS destructors for the whole program) will make it work...

It really was invalid. I was even tracking the `cr_main` pointer for each version and comparing it to `/proc//maps` address spaces of each loaded plugin file. The previous version was...

@MiniaczQ I had that same issue. See PR #21 for a fix.

@tyoc213 You could also try adding a delay to the `UpdateState::Before` handler to give the build system time to finish the build.

@emoon hmm. It might be a safer to watch the `.cargo-lock` file. When `.cargo-lock` is opened, only mark libraries for reload. Then `.cargo-lock` is closed, reload marked libraries.

It could be added as an optional feature. Also I think we could look for `.cargo-lock` in the same folder as the library. When any `.cargo-lock` file is opened, delay...

I think the general case would need to wait X seconds after the last detected change, before reloading. While testing I have seen multiple events trigger a reload, even when...

watching `.cargo-lock` with the Debounce watcher doesn't work, since it is only opened/closed. Would have to switch back to the raw watcher and do our own debouncing.

yes. Hashing would be good. Could do the hash check after shadow copying the lib. 1. Shadow copy. 2. hash copy. 3. wait 100ms. 4. hash original and compare. 5....

`cr` just checks timestamps to detect library changes. One important feature from `cr` is that they version the library file each time they reload. I was just adding timestamps to...