You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. the problem is the same running lua and wlua and running from SciTE.
To test all at once:
cd C:\Program Files\Lua\5.1
2. for %a in ("C:\Program Files\Lua\5.1\examples\wxlua\*.wlua"); do lua "%a"
Some programs work, some crash before starting, some crash when using certain
features.
Since I have Visual Studio installed I get a dialog box asking me if I want to
debug the unhandled exception, and a choice of debuggers.
Unfortunately trying to debug the exceptions isn't illuminating because of a
lack of debug symbols.
What is the expected output? What do you see instead?
an incomplete list of crashes:
bindings.wx.wlua crashed when I double clicked "Overloaded Baseclass Functions"
controls.wx.wlua crashes immediately (but this one gives a lua error after
updating the dlls)
editor.wx.wlua crashed when I selected "comment" from the menu
scribble.wx.wlua, sudoku.wx.wlua and mdi.wx.wlua crashe after a new document is
made
auidemo.wx.wlua when I did something I haven't reproduced...
What version of the product are you using? On what operating system?
Lua_V5.1.4-39.exe
Windows XP Pro, SP 3
Please provide any additional information below.
downloading http://downloads.sourceforge.net/wxlua/wxLua-2.8.10.0-MSW-dll.zip
and replacing the wx dlls from that solves the problem except that
controls.wx.wlua gives an error instead of crashing. Maybe there are files
other than the dlls I need to upgrade.
Also on both versions luamodule.wx.wlua fails on require("wx") unless you put
package.cpath.. at the start of the package.cpath list.
Also there is a problem with debugging wxlua file crashing SciTE but I will
look into that deeper and make another bug report.
Also is it possible to add debugable versions of the libraries and exe's and/or
add external symbol tables that visual studio can read? I noticed that tracing
the exceptions was useless.
Original issue reported on code.google.com by cafealp...@gmail.com on 4 Jul 2010 at 8:43
I forgot to mention that I tried updating the examples in order to see if that
fixed the control.ws.wlua problem. It didn't, but it is true that there are
differences in code on some of the examples.
bindings, scribble, unittest and sudoku have changes. Others show changes but
it's just whitespace.
Original comment by cafealp...@gmail.com on 4 Jul 2010 at 8:46
Wow you are right. I tested this before release, but did not play with the
examples. I just opened them and did minimal tests. Opps. I might role back to
the previous revision until I figure this out. I don't want to deploy the .dlls
that come with the *-MSW-dll download. So I build it myself so that you only
need 3-4 dlls. Much nicer for deployment.
Original comment by rpusz...@gmail.com on 13 Jul 2010 at 1:59
Original issue reported on code.google.com by
cafealp...@gmail.com
on 4 Jul 2010 at 8:43The text was updated successfully, but these errors were encountered: