 |
lua-l archive |
|
|
||
|
|
There are also
changes in luaconf regarding default PATH and CPATH that I had to import in my copy
of the Lua sources, but that’s all. I guess that I can come up with the
DLL myself, it’s just that having it in the LfW distro to begin with
would probably help more people than just me J. Now, I am confused
about the bug I have: If I trim my script
to only use my module with no other module loaded excepted for the standard Lua
libraries, and to run it against my LUA_USE_APICHECK statically linked Lua
interpreter, the bug disappears, and doesn’t seem to be related to an API
error after all. The same test script run against the LfW interpreter seems to
run into some sort of C stack corruption since at some precise point in the
execution of my module, instruction jumps to some irrelevant place when
returning from __alloca_probe in a
function’s prologue. Is there something in the way LfW is built that
could help me understand what is going on? De :
lua-bounces@bazar2.conectiva.com.br
[mailto:lua-bounces@bazar2.conectiva.com.br] De la part de Antonio Scuri I think that
instead of build an new application, you just have to build another DLL and
replace the lua5.1.dll in the main folder and in the clibs folder. If the only
change is LUA_USE_APICHECK I can build a DLL for you, and this DLL can also be
included in future Lfw distributions. Best, scuri |