 |
lua-l archive |
|
|
||
|
http://www.dependencywalker.com/Open your main exe there, press F7, provide arguments, and you might be able to track down how many lua*.dll are there.
Alternatively use SysInternansl ProcExp or NirSoft's CurrProcess (you can google them), and if you are able to somehow stop your app before it's killed (quick Ctrl+S when it prints :)) - then you can also see what DLL's are loaded there (in ProcExp press Ctrl+D)
Furthermore to see what really the file I/O is doing, you can use ProcMon. Press Ctrl+L. Make an application filter on say "lua" (any app that contain lua), include it in the filter and start capturing.
It's a bit like dtrace on unix systems. On 7/8/2011 10:35 PM, Mike Nelson wrote:
My first post to the list (I've been lurking for a few months) I built the rc7 interpreter from source on mingw for Windows Vista 32-bit. require works perfectly for Lua scripts, but on attempting require "lfs", I get this error: C:\Lua52beta-rc7\bin\lua52: multiple Lua VMs detected stack traceback: [C]: in ? [C]: in function 'require' test.lua:4: in main chunk [C]: in ? >Exit code: 1 I made sure that this is the Lua 5.2-compatible version. This file works perfectly with the prebuilt rc5 inerpreter from Lua for Windows. I can't tell if this is a bug or if I made a mistake in building. I haven't used makefiles since college (I'm now retired), so I could easily be doing something wrong. Any help would be much appreciated. -- Mike Nelson