Your `maintenance info sections` output tells us the protection of
0x198f6f7d. Could you also tell us the protection of 0x401bb410? (My
hypothesis being that someone mprotect'ed your lua_State [1] to
read-only, but I don't know who or why)
[1] Actually one of the structures allocated alongside the initial
lua_State, but I digress.
On Fri, Nov 18, 2016 at 11:58 AM, Tomas Kvasnicka <nzt4567@xxxxxxx> wrote:
Hi,
I’ve already tried asking at stackoverflow with no response so I’ll try my
chances over here. Commit ID is 7a58a8fb3d3d5808c54d096ab772113bf9024ae8 but
it has been happening on previous versions of branch 2.1 as well.
Architecture is x86_64, detailed description is at
http://stackoverflow.com/questions/40609455/why-is-this-mov-causing-a-sigsegv ;
and generally any advice is appreciated. I’ve been struggling with this for a
couple of days with no luck so I’ll be glad for any help.
Thanks,
Tomas
