UCAP-DeLuSiOn / luaforwindows

Automatically exported from code.google.com/p/luaforwindows
0 stars 0 forks source link

LuaNet Crashed Apon Require #16

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Whenever luanet or any assembly related to Microsoft.NET is required, Lua 
crashes and poses a bug report. This used to work fine, but then I re-installed 
LuaForWindows from scratch. I have the Lua 5.1 on Windows XP.

Original issue reported on code.google.com by kirkdust...@gmail.com on 30 Jun 2010 at 6:23

GoogleCodeExporter commented 8 years ago

Original comment by rpusz...@gmail.com on 30 Jun 2010 at 7:11

GoogleCodeExporter commented 8 years ago
I've just installed LfW as well, and example 37 in QuickLuaTour crashed 
immediately saying "error loading module 'iuplua' from file 'iuplua51.dll': The 
specified module could not be found." I'm also using LfW v5.1.4-45 on Windows 
XP. After restarting the PC it works. I know there's only a slight chance for 
this piece of information to prove helpful in this case, but maybe it should be 
mentioned somewhere that a restart may be required, as a reminder. Also, if 
this this is what usually happens, maybe you shouldn't even automatically run 
the tour after installation.

Original comment by tikyr...@gmail.com on 17 Aug 2011 at 12:45

GoogleCodeExporter commented 8 years ago
I'm getting the same while using Lua from as an imported dll within my own 
application. The runtime that I use is vc9.

The problem seems though with loading the msvcr80.dll.

If you open lua.exe and luanet.dll in the dependency walker (see pictures), you 
can see that the standalone lua.exe depends on msvcr80.dll and lua5.1.dll, 
which uses msvcr80.dll as well. luanet.dll depends on msvcr80.dll too, however, 
the dependency cannot be resolved. I suspect, this might be the problem.

Original comment by d.ledent...@gmail.com on 17 Oct 2011 at 9:08

Attachments:

GoogleCodeExporter commented 8 years ago
The luanet.dll from LuaInterface_203_LuaForWindows.zip from Issue 35 solved the 
issue for me

Original comment by d.ledent...@gmail.com on 17 Oct 2011 at 9:13