On 03/13/2013 02:50 AM, Gregg Smith wrote: > Hi Daniel, > > I'm seeing segfaults on that dreadful Windows OS when using > LuaMapHandler & LuaRoot together. > Not to worry, I'm seeing seeing this on trunk as well, so it's not your > backport per se. > > Some likely useless info: > http://people.apache.org/~gsmith/httpd/segfault/mod_lua_map_handler_call_stack.txt > > > Cheers, > Gregg > The backtrace was actually quite helpful :) It would appear that the bug (perhaps) pre-dates my work on mod_lua (or it could be something I've missed completely, who knows).
I can see that vm_construct is creating, or attempting to create, a lua VM which returns a null pointer meaning that part failed, but it doesn't check whether the VM is null, making munge_path segfault. At the same time, the lifecycle_pool being passed is also NULL, which makes even less sense to me, since you can see in the backtrace that it wasn't null when it got passed to ap_lua_get_lua_state. Can you tell me which exact lua directives you used for this? which LuaScope, LuaCodeCache and so on? With regards, Daniel.
