lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

No I have only been keeping one instance of Lua on my
computer to avoid this possibility. I make sure to
wipe everything and I haven't built Lua statically
into any of my projects.

I have also verified this crashing behavior with the
stock dll on other Windows computers. 

As for stdout/stderr on Windows, in VC6, if you are
using a console application, it gets mapped to the
console. If you are using a generic Windows
application, a stdout.txt and stderr.txt get created
and the streams go there. I don't do MFC so I don't
know about it, but I think it also does the
stdout.txt/stderr.txt thing.


--- Wim Couwenberg <> wrote:
> Hi,
> > Hmmm. I think I solved both problems. You were
> right
> > Ashwin. After building my own lua.dll and
> lualib.dll
> > instead of using the stock dlls from the Lua
> website,
> > the problem went away for both. So I think there
> is a
> > problem with the stock dll.
> As you are using the dynamic libraries of Lua, I was
> just wondering...
> Could the problem have been that there were several
> incarnations of the
> standard lib around:  one statically linked into the
> Lua DLL and another one
> in your own project (either statically or
> dynamically linked)?  Maybe this
> caused the app to choke when writing to stdout?
> (On a different note:  In a Windows UI app it is not
> clear to what exactly
> stdout (and stderr) is wired, if to anything at all.
>  Just writing to
> stdout/stderr will definitely lead to trouble in
> that setting.)
> Bye,
> Wim

Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.