Alessandro Arzilli
Alessandro Arzilli
That's much better, but the use of reflection is problematic (either arm64asm gets changed or we do an unsafe cast and add a size check on the structs) and wrong...
There was a change fixing a similar bug recently, #3559, did you try building delve from master?
PS. clone the repository and run `make build`.
I'm not sure what that command does anymore, try it with `make build` and post the output of `dlv version`.
Do you have some steps to reproduce this? Does this reproduce with delve 1.22?
Closing, no feedback.
I never looked into what lua_newthread does in detail but wouldn't this imply that all changes we make to our state object need to be under a mutex (with all...
The lua documentation says this: > Creates a new thread, pushes it on the stack, and returns a pointer to a [lua_State](https://www.lua.org/manual/5.3/manual.html#lua_State) that represents this new thread. The new thread...
Suppose something new is registered in a thread and placed in a global variable, does it become available to other threads?
If that is the case the registry needs to be shared between the threads and probably also need synchronization.