Despite extensive logging of every step and details and being partly fixed to allow multiple Lune modules, this bug is outstanding and sadly incredibly puzzling (two Lune module interfere with each other's stack in the Lua machine breaking many things badly... ?!!)
[5.640 debug src/PleineLune.cpp:102 process] Id: 6ed26fd3a9526 Path and script empty, script unloaded 0x12d4970 3771889670505066748
[5.640 debug src/PleineLune.cpp:91 process] 6ed26fd3a9526 requestedSetScript is true
[5.640 debug src/Widgets.hpp:79 operator()] thread is 1527402631159941138
[5.640 debug src/Lune.cpp:272 setScript] 6ed26fd3a9526 Loading
[5.640 debug src/Lune.cpp:274 setScript] Script mutex ok
[5.640 debug src/Lune.cpp:276 setScript] Lua mutex ok
[5.640 warn src/Lune.cpp:288 setScript] Failed opening
[5.640 debug src/Lune.cpp:294 setScript] 6ed26fd3a9526 0x1368070 Content:
[5.641 debug src/Lune.cpp:311 setScript] Debug point 1
[5.641 debug src/Lune.cpp:313 setScript] Script is empty, return from setScript!
[5.641 debug src/PleineLune.cpp:94 process] 6ed26fd3a9526 requestedSetScript is done
[5.641 debug src/PleineLune.cpp:97 process] scriptMutex ok
[5.641 debug src/PleineLune.cpp:99 process] Id: 6ed26fd3a9526 0x1368070 3771889670505066748 luaMutex ok
[5.641 debug src/PleineLune.cpp:102 process] Id: 6ed26fd3a9526 Path and script empty, script unloaded (nil) 3771889670505066748
[5.641 debug src/PleineLune.cpp:97 process] scriptMutex ok
[5.641 debug src/PleineLune.cpp:99 process] Id: 1fcf7e9689d175 0x1378030 4763803445949453583 luaMutex ok
[5.641 debug src/PleineLune.cpp:149 process] Id: 1fcf7e9689d175 0x1378030 Process wasJustSet? 0 4763803445949453583
Thread 23 "Worker 6" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffcf5fb640 (LWP 136841)]
lua_pushvalue (L=0x400f1378, idx=-2) at lj_api.c:180
180 copyTV(L, L->top, index2adr(L, idx));
(gdb) bt
#0 lua_pushvalue (L=0x400f1378, idx=-2) at lj_api.c:180
#1 0x00007fffe90b18ec in LuaJITEngine::process (this=0xe38000) at src/LuaJITEngine.cpp:273
#2 0x00007fffe90c0279 in PleineLune::process (this=0x1377ce0, args=...) at src/PleineLune.cpp:150
#3 0x00007ffff73d83e2 in rack::engine::Module::doProcess(rack::engine::Module::ProcessArgs const&) () from ./libRack.so
#4 0x00007ffff73d1ed1 in rack::engine::EngineWorker::run() () from ./libRack.so
#5 0x00007ffff7835940 in ?? () from ./libRack.so
#6 0x00007ffff6c87b27 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:435
#7 0x00007ffff6d0a78c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb)
Despite extensive logging of every step and details and being partly fixed to allow multiple Lune modules, this bug is outstanding and sadly incredibly puzzling (two Lune module interfere with each other's stack in the Lua machine breaking many things badly... ?!!)