RE: Lua app crash with mixed DLLs; advice needed

[Thijs Schreijer <thijs@...>]

Iirc then it is mostly caused when 'handles' are passed on from one runtime (MSVC runtimes that is) to another. They are not compatible. 
See also; http://www.syndicateofideas.com/posts/fighting-the-msvcrt-dll-hell 

Thijs


> -----Original Message-----
> From: lua-l-bounces@lists.lua.org [mailto:lua-l-bounces@lists.lua.org] On
> Behalf Of Paul K
> Sent: zondag 10 maart 2013 5:26
> To: Lua mailing list
> Subject: Re: Lua app crash with mixed DLLs; advice needed
> 
> Hi Javier,
> 
> > If I understand it correctly, there's no problem if the application
> > uses a luasocker compatible with it, no matter if it's the same as ZB
> > or not. right?
> 
> That's correct.
> 
> > to debug your app, make sure there's a compatible LuaSocket library in
> > the Lua include path...
> 
> That may be fine, but even for love2d users who may be experienced Lua
> developers it may be puzzling suggestion as to what a "compatible"
> library is and where to get it. I can ship two sets of libraries for
> Windows, although I'd prefer to find a configuration that covers all
> possible cases.
> 
> In fact, I haven't seen this issue with VisualStudio compiled luasocket
> (even when used with mingw compiled applications) and am seriously
> considering switching to that configuration, hence the question whether
> this may be problematic for some reason.
> 
> Paul.
> 
> On Sat, Mar 9, 2013 at 7:17 PM, Javier Guerra Giraldez
> <javier@guerrag.com> wrote:
> > On Sat, Mar 9, 2013 at 7:51 PM, Paul K <paulclinger@yahoo.com> wrote:
> >> Here is my situation. ZeroBrane Studio ships with luasocket compiled
> >> using mingw (all other ZBS components are also compiled using the
> >> same compiler). However, a user may debug an application that is
> >> compiled by a different compiler; for example love2d is compiled
> >> using Visual Studio. When the application is being debugged, it loads
> >> luasocket from ZBS (if it's not available in the application)
> >
> >
> > If I understand it correctly, there's no problem if the application
> > uses a luasocker compatible with it, no matter if it's the same as ZB
> > or not. right?
> >
> > then, maybe just a big mention in the docs:
> >
> > ""
> > to debug your app, make sure there's a compatible LuaSocket library in
> > the Lua include path...
> > ""
> >
> >
> >
> > --
> > Javier
> >