[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Application crashes in Windows on Lua print or errors
- From: Eric Wing <ewing2121@...>
- Date: Mon, 27 Jan 2003 14:30:02 -0800 (PST)
Sorry, it just clicked in my head that your were
referring to a statically linked stdio, not Lua.
That I don't know about. I'm not sure how the stock
dll was done. And honestly, I don't know about how
Windows links the stdio library. It's seems so
fundamental to C, that I don't ever think about it or
see people discussing it in Windows.
--- Wim Couwenberg <firstname.lastname@example.org> wrote:
> > Hmmm. I think I solved both problems. You were
> > Ashwin. After building my own lua.dll and
> > instead of using the stock dlls from the Lua
> > 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.)
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.