wxlua-users — wxLua list for users and developers

Re: [wxlua-users] undefined reference to wxLuaState::Ok()

[John L. <jla...@gm...>]

On Sun, Apr 7, 2013 at 2:41 PM, andreas graeper <agr...@go...> wrote:
>
> g++
>  -o ../bin/wxlua
>  app_wxlua_lconsole.o
>  app_wxlua_wxlua.o
>
...
> lconsole.cpp:(.text+0x53e): undefined reference to `wxLuaState::Ok() const'
...
> libwxlua_gtk2u_wxlua-2.8.so:000000000001fc90 T _ZNK10wxLuaState2OkEv
...
> symbol should be defined in libwxlua_gtk2u_wxlua-2.8.so ?!

It should be and looks like it is. How did you build wxLua? Did you
build wxLua libs and apps using the CMake build files?

Regards,
    John

[wxlua-users] undefined reference to wxLuaState::Ok()

[andreas g. <agr...@go...>]

g++
 -o ../bin/wxlua
 app_wxlua_lconsole.o
 app_wxlua_wxlua.o

 -L/usr/lib
 -L../lib
 -L/home/arno/lua/ide/wxlua/wxLua/lib

 -lwxlua_gtk2u_wxbindxrc-2.8
 -lwxlua_gtk2u_wxbindstc-2.8
 -lwxlua_gtk2u_wxbindrichtext-2.8
 -lwxlua_gtk2u_wxbindmedia-2.8
 -lwxlua_gtk2u_wxbindhtml-2.8
 -lwxlua_gtk2u_wxbindgl-2.8
 -lwxlua_gtk2u_wxbindaui-2.8
 -lwxlua_gtk2u_wxbindadv-2.8
 -lwxlua_gtk2u_wxbindxml-2.8
 -lwxlua_gtk2u_wxbindnet-2.8
 -lwxlua_gtk2u_wxbindcore-2.8
 -lwxlua_gtk2u_wxbindbase-2.8
 -lwxlua_gtk2u_wxluasocket-2.8
 -lwxlua_gtk2u_wxluadebug-2.8
 -lwxlua_gtk2u_wxlua-2.8
 -llua5.1

 -L/usr/lib/x86_64-linux-gnu -pthread
 -L/usr/lib/x86_64-linux-gnu

 -lwx_gtk2u_stc-2.8
 -lwx_gtk2u_richtext-2.8
 -lwx_gtk2u_xrc-2.8
 -lwx_baseu_xml-2.8
 -lwx_baseu_net-2.8
 -lwx_gtk2u_media-2.8
 -lwx_gtk2u_html-2.8
 -lwx_gtk2u_gl-2.8
 -lwx_gtk2u_aui-2.8
 -lwx_gtk2u_adv-2.8
 -lwx_gtk2u_core-2.8
 -lwx_baseu-2.8

app_wxlua_lconsole.o: In function `wxLuaConsole::DisplayStack(wxLuaState
const&)':
lconsole.cpp:(.text+0x53e): undefined reference to `wxLuaState::Ok() const'
app_wxlua_wxlua.o: In function `wxLuaStandaloneApp::DisplayMessage(wxString
const&, bool, wxLuaState const&)':
wxlua.cpp:(.text+0x397): undefined reference to `wxLuaState::Ok() const'
app_wxlua_wxlua.o: In function `wxLuaStandaloneApp::OnInit()':
wxlua.cpp:(.text+0x86c): undefined reference to `wxLuaState::Ok() const'


nm lib/*.so shows :

libwxlua_gtk2u_wxbindadv-2.8.so:                 U _ZNK10wxLuaState2OkEv
libwxlua_gtk2u_wxbindbase-2.8.so:                 U _ZNK10wxLuaState2OkEv
libwxlua_gtk2u_wxbindcore-2.8.so:                 U _ZNK10wxLuaState2OkEv
libwxlua_gtk2u_wxbindhtml-2.8.so:                 U _ZNK10wxLuaState2OkEv
libwxlua_gtk2u_wxlua-2.8.so:000000000001fc90 T _ZNK10wxLuaState2OkEv
libwxlua_gtk2u_wxluadebug-2.8.so:                 U _ZNK10wxLuaState2OkEv
wx.so:                 U _ZNK10wxLuaState2OkEv

symbol should be defined in libwxlua_gtk2u_wxlua-2.8.so ?!

Re: [wxlua-users] compliling for 5.2

[John L. <jla...@gm...>]

On Tue, Apr 2, 2013 at 11:31 AM, Victor Bombi <so...@te...> wrote:
>> Can you explain why these other modules cannot work with
>> LUA_COMPAT_ALL enabled? Are they providing their own duplicate
>> versions of Lua's functions and you get linker errors?
>>
>> Also, can you explain line 25 here?
>> https://github.com/diegonehab/luasocket/blob/unstable/src/luasocket.h
>>
> That true luasocket seems to need LUA_COMPAT_ALL

Actually, only LUA_COMPAT_MODULE which LUA_COMPAT_ALL enables, but the
bottom line is that you can probably expect that system installed Lua
libraries (on Linux) will have LUA_COMPAT_ALL enabled so Lua Lanes
will probably want to figure out some workaround in the long run
(unless they wait all the way until 5.3 which could be years away).

> This is the explanation for Lua Lanes:
>
> Lua 5.2 introduced a hash randomizer seed which causes table iteration to
> yield a different key order on different VMs even when the tables are
> populated the exact same way. When Lua is built with compatibility options
> (such as LUA_COMPAT_ALL), this causes several base libraries to register
> functions under multiple names. This, with the randomizer, can cause the
> first encountered name of a function to be different on different VMs, which
> breaks function transfer. This means that Lua 5.2 must be built WITHOUT
> compatibility options to be able to use Lanes. Even under Lua 5.1, this may
> cause trouble (even if this would be much less frequent). Unfortunately, we
> get bitten by string.gfind/string.gmatch when Lua 5.1 is built with
> LUA_COMPAT_GFIND (which is the case of LuaBinaries), so for the time being,
> Lanes fails only for Lua 5.2 as the randomizer is the real show breaker
> here.

I do remember something about the hash randomizer for security on the
Lua list, but I didn't read that thread...

It looks like all Lua Lanes cares about is that function names don't change.

See the comment above and the code below :
    if( (LUA_VERSION_NUM > 501) && (prevName != NULL))
Here :
    https://github.com/LuaLanes/lanes/blob/master/src/tools.c

Finally see the code for LUA_COMPAT_ALL here :

http://www.lua.org/source/5.2/luaconf.h.html

Maybe the offending define is LUA_COMPAT_MODULE, which of course, is
exactly the one that every Lua library that wants to stay compatible
with 5.1 and 5.2 will use. However, the check in Lua lanes is not for
any COMPAT define, but rather that you aren't calling the same
function with a different name.

The solution may be quite simple, always use the same name when
calling any particular function and you won't trigger the Lua Lanes
error. Off the top of my head I don't see why, technically, they care
what the name of the function is, but that might be something to look
into too. I would ask on the Lua Lanes mailing list, or wherever would
be appropriate, for a clarification of this statement; "causes several
base libraries to register functions under multiple names." Ideally,
people would need to know what the names of these multiply named
functions are so they can avoid the problem altogether.

Do you actually get an error now? And if so, for what function? Maybe
log() and log10() ?

----------------------------

Something to try... Do you get an error in Lua Lanes if you do
something like this?

string_format = string.format
local local_string_format = string.format

print("a", string.format("%d", 1))
print("b", string_format("%d", 1))
print("c", local_string_format("%d", 1))

Regards,
    John

Re: [wxlua-users] compliling for 5.2

[Victor B. <so...@te...>]

> Can you explain why these other modules cannot work with
> LUA_COMPAT_ALL enabled? Are they providing their own duplicate
> versions of Lua's functions and you get linker errors?
>
> Also, can you explain line 25 here?
> https://github.com/diegonehab/luasocket/blob/unstable/src/luasocket.h
>

That true luasocket seems to need LUA_COMPAT_ALL

This is the explanation for Lua Lanes:

Lua 5.2 introduced a hash randomizer seed which causes table iteration to 
yield a different key order on different VMs even when the tables are 
populated the exact same way. When Lua is built with compatibility options 
(such as LUA_COMPAT_ALL), this causes several base libraries to register 
functions under multiple names. This, with the randomizer, can cause the 
first encountered name of a function to be different on different VMs, which 
breaks function transfer. This means that Lua 5.2 must be built WITHOUT 
compatibility options to be able to use Lanes. Even under Lua 5.1, this may 
cause trouble (even if this would be much less frequent). Unfortunately, we 
get bitten by string.gfind/string.gmatch when Lua 5.1 is built with 
LUA_COMPAT_GFIND (which is the case of LuaBinaries), so for the time being, 
Lanes fails only for Lua 5.2 as the randomizer is the real show breaker 
here.

For me Lanes is the most essential module in Lua.

Victor Bombi

Re: [wxlua-users] compliling for 5.2

[John L. <jla...@gm...>]

On Mon, Apr 1, 2013 at 4:46 AM, Victor Bombi <so...@te...> wrote:
>
> perhaps luaL_requiref is the answer?

Eventually, but I'd prefer to not reimplement perfectly good existing
code that is enabled by default.

>>I recompiled lua52 with LUA_COMPAT_ALL and managed to compile wx.lua
>> The problem I have is that I use other lua modules also: Lanes, Luasocket
>> ...
>> Lanes cant be used with LUA_COMPAT_ALL (only pure 5.1 or 5.2) so I wont be
>> able
>> to use 5.2 in my project.
>> Looking into the future I thing that wxlua should get rid of
>> LUA_COMPAT_ALL
>> to be compatible
>> with other modules.

Actually, it's the other modules that need to be compatible with Lua
and wxLua since the Lua Makefile default is LUA_COMPAT_ALL and I would
assume that OS packagers would respect the Lua Makefile and keep it
enabled. If you're correct, this means that these libraries won't work
using a default system Lua library?

Can you explain why these other modules cannot work with
LUA_COMPAT_ALL enabled? Are they providing their own duplicate
versions of Lua's functions and you get linker errors?

Also, can you explain line 25 here?
https://github.com/diegonehab/luasocket/blob/unstable/src/luasocket.h

Regards,
     John

Re: [wxlua-users] compliling for 5.2

[Victor B. <so...@te...>]

perhaps luaL_requiref is the answer?

>I recompiled lua52 with LUA_COMPAT_ALL and managed to compile wx.lua
> The problem I have is that I use other lua modules also: Lanes, Luasocket
> ...
> Lanes cant be used with LUA_COMPAT_ALL (only pure 5.1 or 5.2) so I wont be
> able
> to use 5.2 in my project.
> Looking into the future I thing that wxlua should get rid of 
> LUA_COMPAT_ALL
> to be compatible
> with other modules.
>
> Best
> victor

Re: [wxlua-users] compliling for 5.2

[Victor B. <so...@te...>]

I recompiled lua52 with LUA_COMPAT_ALL and managed to compile wx.lua
The problem I have is that I use other lua modules also: Lanes, Luasocket 
...
Lanes cant be used with LUA_COMPAT_ALL (only pure 5.1 or 5.2) so I wont be 
able
to use 5.2 in my project.
Looking into the future I thing that wxlua should get rid of LUA_COMPAT_ALL 
to be compatible
with other modules.

Best
victor 

Re: [wxlua-users] compliling for 5.2

[John L. <jla...@gm...>]

On Sun, Mar 31, 2013 at 12:29 PM, Victor Bombi <so...@te...> wrote:
> after commenting all inicializations. Compile is ok but
>
> CMakeFiles\wxLuaModule.dir/objects.a(wxlbind.cpp.obj):wxlbind.cpp:(.text+0x1f2):
> undefined reference to `_luaL_openlib'
>
> I think that luaL_openlib was deprecated for luaL_register in 5.1 and for
> luaL_setfuncs in 5.2

It is deprecated, but luaL_setfuncs() is not a suitable replacement
since it doesn't set the package.loaded table. I think the best option
is to leave the code as is and use Lua's backward compatible functions
for the near future.

Did you change Lua's Makefile to not #define LUA_COMPAT_ALL? By
default it is set and you'll need to set it back to link to wxLua.

CFLAGS= -O2 -Wall -DLUA_COMPAT_ALL $(SYSCFLAGS) $(MYCFLAGS)

Regards,
     John

Re: [wxlua-users] compliling for 5.2

[Victor B. <so...@te...>]

after commenting all inicializations. Compile is ok but

Linking CXX shared library ..\..\bin\Release\wx.dll
cd /d C:\LUA\wxlua-sources\buildzzz2\modules\luamodule && "C:\Program 
Files\CMake 2.8\bin\cmake.exe" -E cmake_link_script CMa
keFiles\wxLuaModule.dir\link.txt --verbose=1
"C:\Program Files\CMake 2.8\bin\cmake.exe" -E remove -f 
CMakeFiles\wxLuaModule.dir/objects.a
C:\MinGWORI\bin\ar.exe cr CMakeFiles\wxLuaModule.dir/objects.a 
@CMakeFiles\wxLuaModule.dir\objects1.rsp
C:\MinGWORI\bin\g++.exe     -shared -o 
..\..\bin\Release\wx.dll -Wl,--out-implib,..\..\lib\Release\libwx.dll.a -Wl,--major-im
age-version,0,--minor-image-version,0 -Wl,--whole-archive 
CMakeFiles\wxLuaModule.dir/objects.a -Wl,--no-whole-archive C:\LUA\
lua-5.2.2\build2\liblua52.dll.a 
C:\wxWidgets-2.8.12\lib\gcc_lib\libwxmsw28u_xrc.a 
C:\wxWidgets-2.8.12\lib\gcc_lib\libwxbase28
u_xml.a C:\wxWidgets-2.8.12\lib\gcc_lib\libwxbase28u_net.a 
C:\wxWidgets-2.8.12\lib\gcc_lib\libwxmsw28u_media.a C:\wxWidgets-2
.8.12\lib\gcc_lib\libwxmsw28u_richtext.a 
C:\wxWidgets-2.8.12\lib\gcc_lib\libwxmsw28u_aui.a 
C:\wxWidgets-2.8.12\lib\gcc_lib\li
bwxmsw28u_stc.a C:\wxWidgets-2.8.12\lib\gcc_lib\libwxmsw28u_html.a 
C:\wxWidgets-2.8.12\lib\gcc_lib\libwxmsw28u_adv.a C:\wxWid
gets-2.8.12\lib\gcc_lib\libwxmsw28u_core.a 
C:\wxWidgets-2.8.12\lib\gcc_lib\libwxbase28u.a 
C:\wxWidgets-2.8.12\lib\gcc_lib\lib
wxpng.a C:\wxWidgets-2.8.12\lib\gcc_lib\libwxtiff.a 
C:\wxWidgets-2.8.12\lib\gcc_lib\libwxjpeg.a C:\wxWidgets-2.8.12\lib\gcc_l
ib\libwxzlib.a C:\wxWidgets-2.8.12\lib\gcc_lib\libwxregexu.a 
C:\wxWidgets-2.8.12\lib\gcc_lib\libwxexpat.a -lwinmm -lcomctl32
-lrpcrt4 -lwsock32 -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32  
-loleaut32 -luuid -lcomdlg32 -ladvapi32
Creating library file: ..\..\lib\Release\libwx.dll.a
CMakeFiles\wxLuaModule.dir/objects.a(wxlbind.cpp.obj):wxlbind.cpp:(.text+0x1f2): 
undefined reference to `_luaL_openlib'
CMakeFiles\wxLuaModule.dir/objects.a(wxlstate.cpp.obj):wxlstate.cpp:(.text+0x74): 
undefined reference to `_luaL_openlib'
CMakeFiles\wxLuaModule.dir/objects.a(wxlstate.cpp.obj):wxlstate.cpp:(.text+0xa109): 
undefined reference to `_luaL_openlib'
collect2.exe: error: ld returned 1 exit status

I think that luaL_openlib was deprecated for luaL_register in 5.1 and for 
luaL_setfuncs in 5.2

Best
victor 

Re: [wxlua-users] compliling for 5.2

[Victor B. <so...@te...>]

> I see that on that line I am trying to properly initialize a lua_Debug
> struct, probably the struct has changed since 5.1? You can rem that
> line out for now...

As far as I know it is not unsigned char.
After removing inicialization I get

C:\LUA\wxlua-sources\wxlua\wxLua\modules\wxlua\debug\wxldebug.cpp: In member 
function 'int wxLuaDebugData::EnumerateStack(lua
_State*)':
C:\LUA\wxlua-sources\wxlua\wxLua\modules\wxlua\debug\wxldebug.cpp:177:26: 
error: braces around scalar initializer for type 'u
nsigned char'
C:\LUA\wxlua-sources\wxlua\wxLua\modules\wxlua\debug\wxldebug.cpp: In member 
function 'int wxLuaDebugData::EnumerateStackEntr
y(lua_State*, int, wxArrayInt&)':
C:\LUA\wxlua-sources\wxlua\wxLua\modules\wxlua\debug\wxldebug.cpp:218:26: 
error: braces around scalar initializer for type 'u
nsigned char' 

Re: [wxlua-users] svn request password

[Paul K <pau...@ya...>]

Hi John,

As far as I understand, wxstedit is only needed when wxlua is compiled
with wxwidgets 2.8.12; it's no longer required for 2.9.x. Or am I
mistaken?

If it's not needed for 2.9.x, then "svn checkout --ignore-externals"
can probably be used to skip it (I can't test it at the moment).

Paul.

On Sat, Mar 30, 2013 at 12:49 PM, John Labenski <jla...@gm...> wrote:
> On Sat, Mar 30, 2013 at 2:27 PM, Victor Bombi <so...@te...> wrote:
>>
>>> Is this for wxstedit? The external in wxLua/modules? Try deleting the
>>> wxLua/modules/wxstedit dir and update again.
>>>
>> Yes, it is related to wxstedit. I did a new svn checkout and it does not
>> work
>
> I will change the svn:externals to use http and not https... sigh. You
> may have to delete wxLua/modules/wxstedit and recheckout.
>
>
> For future reference:
>
> https://sourceforge.net/p/forge/site-support/2768/
> http://sourceforge.net/apps/trac/sourceforge/ticket/19669
>
> Hopefully this will be fixed soon.
>
> Regards,
>     John
>
> ------------------------------------------------------------------------------
> Own the Future-Intel(R) Level Up Game Demo Contest 2013
> Rise to greatness in Intel's independent game demo contest. Compete
> for recognition, cash, and the chance to get your game on Steam.
> $5K grand prize plus 10 genre and skill prizes. Submit your demo
> by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] compliling for 5.2

[John L. <jla...@gm...>]

On Sat, Mar 30, 2013 at 11:35 AM, Victor Bombi <so...@te...> wrote:
> Hello,
>
> It worked when compiling for 5.1, but with 5.2 I get:
>
> O3 -DNDEBUG @CMakeFiles/wxLuaLib.dir/includes_CXX.rsp   -o
> CMakeFiles\wxLuaLib.dir\wxlconsole.cpp.obj -c C:\LUA\wxlua-sources
> \wxlua\wxLua\modules\wxlua\wxlconsole.cpp
> C:\LUA\wxlua-sources\wxlua\wxLua\modules\wxlua\wxlconsole.cpp: In member
> function 'void wxLuaConsole::DisplayStack(const wxLu
> aState&)':
> C:\LUA\wxlua-sources\wxlua\wxLua\modules\wxlua\wxlconsole.cpp:233:26: error:
> braces around scalar initializer for type 'unsig
> ned char'
> In file included from
> C:\LUA\wxlua-sources\wxlua\wxLua\modules\wxlua\wxlconsole.cpp:21:0:
> C:/LUA/wxlua-sources/wxlua/wxLua/art/wxlua.xpm: At global scope:
> C:/LUA/wxlua-sources/wxlua/wxLua/art/wxlua.xpm:2:21: warning: 'LUA_xpm'
> defined but not used [-Wunused-variable]
> mingw32-make[2]: ***

I don't have any time today, but I remember seeing something about
"braces ... scaler initializer" on the Lua mailing list after the
release of 5.2.

I see that on that line I am trying to properly initialize a lua_Debug
struct, probably the struct has changed since 5.1? You can rem that
line out for now...

lua_Debug luaDebug = INIT_LUA_DEBUG;


Regards,
    John

Re: [wxlua-users] svn request password

[John L. <jla...@gm...>]

On Sat, Mar 30, 2013 at 2:27 PM, Victor Bombi <so...@te...> wrote:
>
>> Is this for wxstedit? The external in wxLua/modules? Try deleting the
>> wxLua/modules/wxstedit dir and update again.
>>
> Yes, it is related to wxstedit. I did a new svn checkout and it does not
> work

I will change the svn:externals to use http and not https... sigh. You
may have to delete wxLua/modules/wxstedit and recheckout.


For future reference:

https://sourceforge.net/p/forge/site-support/2768/
http://sourceforge.net/apps/trac/sourceforge/ticket/19669

Hopefully this will be fixed soon.

Regards,
    John

Re: [wxlua-users] svn request password

[Victor B. <so...@te...>]

> Is this for wxstedit? The external in wxLua/modules? Try deleting the
> wxLua/modules/wxstedit dir and update again.
>
Yes, it is related to wxstedit. I did a new svn checkout and it does not 
work

victor 

Re: [wxlua-users] svn request password

[John L. <jla...@gm...>]

On Sat, Mar 30, 2013 at 12:16 PM, Victor Bombi <so...@te...> wrote:
> Hello,
>
> I cant get the lattest svn : a password and user is requested

Is this for wxstedit? The external in wxLua/modules? Try deleting the
wxLua/modules/wxstedit dir and update again.

Sourceforge changed their repo address for their new "platform" and
wxCode updated to to, but wxLua has not yet.

http://sourceforge.net/apps/trac/sourceforge/wiki/Subversion#Access
The claim is that "No username and password will be requested when
performing read operations."

Is this not true?

I will try to delete my stored passwords and try as a "normal" user.

Regards,
    John

[wxlua-users] svn request password

[Victor B. <so...@te...>]

Hello,

I cant get the lattest svn : a password and user is requested

Best
victor bombi

[wxlua-users] compliling for 5.2

[Victor B. <so...@te...>]

Hello,

My CMAKE command line is:

"C:\Program Files\CMake 2.8\bin\cmake"  -G"MinGW Makefiles" -DCMAKE_BUILD_TYPE=Release  -DwxWidgets_ROOT_DIR=C:/wxWidgets-2.8.12/ -DwxWidgets_LIB_DIR=C:/wxWidgets-2.8.12/lib/gcc_lib -DwxWidgets_CONFIGURATION=mswu -D wxWidgets_VERSION=2.8.x -DBUILD_VERBOSELY=TRUE -DBUILD_SHARED_LIBS=FALSE  -DwxLua_LUA_LIBRARY_VERSION=5.2 -DwxLua_LUA_LIBRARY_USE_BUILTIN=FALSE -DwxLua_LUA_LIBRARY=C:/LUA/lua-5.2.2/build2/liblua52.dll.a -DwxLua_LUA_INCLUDE_DIR=C:/LUA/lua-5.2.2/src ../wxlua/wxlua

It worked when compiling for 5.1, but with 5.2 I get:

[ 20%] Building CXX object modules/wxlua/CMakeFiles/wxLuaLib.dir/wxlconsole.cpp.obj
cd /d C:\LUA\wxlua-sources\buildzzz2\modules\wxlua && C:\MinGWORI\bin\g++.exe   -DUNICODE -D_UNICODE -DwxUSE_UNICODE=1 -DwxLU
A_USEBINDING_WXGL=0 -DwxLUA_USEBINDING_WXSTC=1 -DwxLUA_USEBINDING_WXXRC=1 -DwxLUA_USEBINDING_WXRICHTEXT=1 -DwxLUA_USEBINDING_
WXHTML=1 -DwxLUA_USEBINDING_WXMEDIA=1 -DwxLUA_USEBINDING_WXAUI=1 -DwxLUA_USEBINDING_WXADV=1 -DwxLUA_USEBINDING_WXCORE=1 -DwxL
UA_USEBINDING_WXXML=1 -DwxLUA_USEBINDING_WXNET=1 -DwxLUA_USEBINDING_WXBASE=1 -DwxLUA_USEBINDING_WXGL=0 -DwxLUA_USEBINDING_WXS
TC=1 -DwxLUA_USEBINDING_WXXRC=1 -DwxLUA_USEBINDING_WXRICHTEXT=1 -DwxLUA_USEBINDING_WXHTML=1 -DwxLUA_USEBINDING_WXMEDIA=1 -Dwx
LUA_USEBINDING_WXAUI=1 -DwxLUA_USEBINDING_WXADV=1 -DwxLUA_USEBINDING_WXCORE=1 -DwxLUA_USEBINDING_WXXML=1 -DwxLUA_USEBINDING_W
XNET=1 -DwxLUA_USEBINDING_WXBASE=1 -DwxLUA_USEBINDING_WXGL=0 -DwxLUA_USEBINDING_WXSTC=1 -DwxLUA_USEBINDING_WXXRC=1 -DwxLUA_US
EBINDING_WXRICHTEXT=1 -DwxLUA_USEBINDING_WXHTML=1 -DwxLUA_USEBINDING_WXMEDIA=1 -DwxLUA_USEBINDING_WXAUI=1 -DwxLUA_USEBINDING_
WXADV=1 -DwxLUA_USEBINDING_WXCORE=1 -DwxLUA_USEBINDING_WXXML=1 -DwxLUA_USEBINDING_WXNET=1 -DwxLUA_USEBINDING_WXBASE=1 -Wall -
O3 -DNDEBUG @CMakeFiles/wxLuaLib.dir/includes_CXX.rsp   -o CMakeFiles\wxLuaLib.dir\wxlconsole.cpp.obj -c C:\LUA\wxlua-sources
\wxlua\wxLua\modules\wxlua\wxlconsole.cpp
C:\LUA\wxlua-sources\wxlua\wxLua\modules\wxlua\wxlconsole.cpp: In member function 'void wxLuaConsole::DisplayStack(const wxLu
aState&)':
C:\LUA\wxlua-sources\wxlua\wxLua\modules\wxlua\wxlconsole.cpp:233:26: error: braces around scalar initializer for type 'unsig
ned char'
In file included from C:\LUA\wxlua-sources\wxlua\wxLua\modules\wxlua\wxlconsole.cpp:21:0:
C:/LUA/wxlua-sources/wxlua/wxLua/art/wxlua.xpm: At global scope:
C:/LUA/wxlua-sources/wxlua/wxLua/art/wxlua.xpm:2:21: warning: 'LUA_xpm' defined but not used [-Wunused-variable]
mingw32-make[2]: *** [modules/wxlua/CMakeFiles/wxLuaLib.dir/wxlconsole.cpp.obj] Error 1
mingw32-make[2]: Leaving directory `C:/LUA/wxlua-sources/buildzzz2'
mingw32-make[1]: *** [modules/wxlua/CMakeFiles/wxLuaLib.dir/all] Error 2
mingw32-make[1]: Leaving directory `C:/LUA/wxlua-sources/buildzzz2'
mingw32-make: *** [all] Error 2

Best Regards
victor bombi

Re: [wxlua-users] wxLua Windows Binaries from 2004/2005

[Reinhard P. [W. Rabbit] <rei...@wh...>]

  

I have that version already. Unfortunately it doesnt help.
So if
anybody kept older versions it would be great if he can share.


Best,
Reinhard 

Am 22.03.2013 00:18, schrieb John Labenski: 

> On
Thu, Mar 21, 2013 at 7:26 AM, Reinhard Pollice [White Rabbit]
> wrote:
>

>> Hey, I need wxLua Binary versions from 2004/2005. Reason I need it
is that for a specific tool we wrote which seems to have problems with
newer wxLua versions. Would be great if somebody still has kept those
old stuff.
> 
> I don't think I have copy of a binary that old anymore,
but there is a
> version from 2006 that might not be too different.
> 
>
http://sourceforge.net/projects/wxlua/files/wxlua/ [2]
> 
> Regards,
>
John
> 
>
------------------------------------------------------------------------------
>
Everyone hates slow websites. So do we.
> Make your web apps faster
with AppDynamics
> Download AppDynamics Lite for free today:
>
http://p.sf.net/sfu/appdyn_d2d_mar [3]
>
_______________________________________________
> wxlua-users mailing
list
> wxl...@li... [4]
>
https://lists.sourceforge.net/lists/listinfo/wxlua-users [5]



Links:
------
[1] mailto:rei...@wh...
[2]
http://sourceforge.net/projects/wxlua/files/wxlua/
[3]
http://p.sf.net/sfu/appdyn_d2d_mar
[4]
mailto:wxl...@li...
[5]
https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] wxLua Windows Binaries from 2004/2005

[John L. <jla...@gm...>]

On Thu, Mar 21, 2013 at 7:26 AM, Reinhard Pollice [White Rabbit]
<rei...@wh...> wrote:
> Hey,
>
> I need wxLua Binary versions from 2004/2005. Reason I need it is that for a
> specific tool we wrote which seems to have problems with newer wxLua
> versions.
> Would be great if somebody still has kept those old stuff.

I don't think I have copy of a binary that old anymore, but there is a
version from 2006 that might not be too different.

http://sourceforge.net/projects/wxlua/files/wxlua/

Regards,
    John

[wxlua-users] wxLua Windows Binaries from 2004/2005

[Reinhard P. [W. Rabbit] <rei...@wh...>]

  

Hey, 

I need wxLua Binary versions from 2004/2005. Reason I need
it is that for a specific tool we wrote which seems to have problems
with newer wxLua versions.
Would be great if somebody still has kept
those old stuff. 

Best,
Reinhard 
  

Re: [wxlua-users] Segfaults in wxlua on Linux (when using "assert" or "return")

[Paul K <pau...@ya...>]

Hi John,

> Note that I'm in the build-2.9-wx_gtk2/lib/Debug dir and run $gdb
> ../../bin/Debug/lua. That could also be a problem, are you building
> using one version/build of Lua then running with a different one?

Thank you for checking... Good to hear that it's working for you. I
suspected that something could be wrong with the way I'm building it,
but all my other tests (and the entire application) are working
without issues. I'm building lua with the same command; although I
used a copy from one of the previous builds, but none of the lua
settings have changed. I'll do some further testing, but so far my
builds still show the same issue.

Paul.

On Mon, Mar 18, 2013 at 4:02 PM, John Labenski <jla...@gm...> wrote:
> On Mon, Mar 18, 2013 at 5:29 PM, Paul K <pau...@ya...> wrote:
>> Hi John,
>>
>> I'm using assert() to check some of the conditions in my code before I
>> start the event loop and noticed that when the script exits after
>> "require 'wx'", but before the main loop is started, it triggers
>> segfault on Linux (tested on Fedora 18, but I saw the same thing on
>> Ubuntu).
>
> Well, I'm not sure there is much difference between what is happening
> and what you're asking to happen by calling assert(), which is to
> terminate the program violently. But, in any case, I don't get the
> same result so I suspect something is wrong with your build. I would
> review your build and clean and rebuild it after sorting out any
> inconsistencies with multiple png libs or anything else like that.
>
> I just tried the program "test.lua" using the lastest wxLua SVN using
> wxLua's provided Lua5.1 in CentOS 6. (I just noticed that you have to
> do "mv libwx.so wx.so", I will fix that)
>
> -- ------------------------------------------------------
> -- test.lua
> local wx = require("wx")
> --os.exit()
> --assert(false)
> --return
> print("hello")
> -- ------------------------------------------------------
>
> Note that I'm in the build-2.9-wx_gtk2/lib/Debug dir and run $gdb
> ../../bin/Debug/lua. That could also be a problem, are you building
> using one version/build of Lua then running with a different one?
>
> -- THIS HAS os.exit() unremmed
> (gdb) run test.lua
> Starting program:
> /home/john/wx/wx-svn/wx-svn/wx/build-2.9-wx_gtk2/bin/Debug/lua
> test.lua
> [Thread debugging using libthread_db enabled]
> Program exited normally.
>
> -- THIS HAS assert(false) unremmed
> (gdb) run test.lua
> Starting program:
> /home/john/wx/wx-svn/wx-svn/wx/build-2.9-wx_gtk2/bin/Debug/lua
> test.lua
> [Thread debugging using libthread_db enabled]
> /home/john/wx/wx-svn/wx-svn/wx/build-2.9-wx_gtk2/bin/Debug/lua:
> test.lua:5: assertion failed!
> stack traceback:
>         [C]: in function 'assert'
>         test.lua:5: in main chunk
>         [C]: ?
>
> Program exited with code 01.
>
> -- THIS HAS return unremmed
> (gdb) run test.lua
> Starting program:
> /home/john/wx/wx-svn/wx-svn/wx/build-2.9-wx_gtk2/bin/Debug/lua
> test.lua
> [Thread debugging using libthread_db enabled]
> hello
> Program exited normally.
>
> -- THIS just lets it run through.
> (gdb) run test.lua
> Starting program:
> /home/john/wx/wx-svn/wx-svn/wx/build-2.9-wx_gtk2/bin/Debug/lua
> test.lua
> [Thread debugging using libthread_db enabled]
> hello
> Program exited normally.
> (gdb)
>
> ----------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] How to configure wxlua to *not* link wxpng library?

[Paul K <pau...@ya...>]

Hi John,

> wxLua does not have switches "--with-libpng" are you talking about
> building the wxWidgets library?

yes; my apologies this wasn't clear.

>> I ended up patching the makefile
>> (luamodule/CMakeFiles/wxLuaModules.dir/link.txt), but would prefer
>> something a bit more robust.
>
> This is not a good idea.

I agree; it wasn't my preference.

> to fix it by using the system libs. Hint: don't specify --with-libpng
> at all and last few lines of the output of configure tells you what
> will be used. Don't forget to clean or preferably delete the old

I'll try that, but I wanted to be explicit in my file that I want to
use the system library.

>>> force) to exclude wxpng from the link command, but failed. Ideally
>>> wxlua should somehow check if the library is configured as "builtin"
>>> or "sys", but for now I just need to check if this is going to work
>
> Check what and from whom?

> http://wxlua.sourceforge.net/docs/install.html#C2.5

Check that wxpng-* library should not be linked into wx.so. I did read
the documentation, but I missed a warning in the ./configure output
that indicated that "system png library will not be used without
system zlib" and as the result wxwidgets was using system png library,
so I was fighting against that.

Thank you John for clarifying this. I'm rebuilding with (more)
appropriate settings...

Paul.

On Mon, Mar 18, 2013 at 3:28 PM, John Labenski <jla...@gm...> wrote:
> On Mon, Mar 18, 2013 at 1:55 AM, Paul K <pau...@ya...> wrote:
>> Hi John,
>>
>> I ended up patching the makefile
>> (luamodule/CMakeFiles/wxLuaModules.dir/link.txt), but would prefer
>> something a bit more robust.
>
> This is not a good idea.
>
>> On Sun, Mar 17, 2013 at 9:58 AM, Paul K <pau...@ya...> wrote:
>>> Hi John,
>>>
>>> I ran into an issue with configuring wxlua to use system libpng
>>> library. I tried both --with-libpng=builtin and --with-libpng=sys, but
>>> I get exactly the same result.
>
> wxLua does not have switches "--with-libpng" are you talking about
> building the wxWidgets library?
>
>>> This discussion
>>> (https://groups.google.com/forum/?fromgroups=#!topic/wx-users/2QWQD0qUVUc)
>>> indicates that it's better to use a system library, but I can't
>
> Yes, it nearly always is best to use the system libraries for such
> basic libs (zlib, png, tiff, jpeg, and gtk).
>
> Reread that thread, it explains exactly what your problem is and how
> to fix it by using the system libs. Hint: don't specify --with-libpng
> at all and last few lines of the output of configure tells you what
> will be used. Don't forget to clean or preferably delete the old
> wxWidgets build dir to be sure that you're getting what you think
> you're getting.
>
>>> configure wxlua to *not* link builtin library as can be see from this
>>> output from cmake:
>>>
>>> -- * - wxWidgets_LIBRARIES         =
>>> -L/home/paul/zbs/build/deps/lib;-pthread;;;/home/paul/zbs/build/deps/lib
>>> /libwx_gtk2u_stc-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_aui-2.9.a;/home/paul/zbs/build/deps/lib
>>> /libwx_baseu_net-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_html-2.9.a;/home/paul/zbs/build/deps/lib
>>> /libwx_gtk2u_adv-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_core-2.9.a;/home/paul/zbs/build/deps/lib
>>> /libwx_baseu-2.9.a;-lwxscintilla-2.9;-pthread;-lgthread-2.0;-lrt;-lX11;-lXxf86vm;-lgtk-x11-2.0;-lgdk-x11-2.0;-latk-
>>> 1.0;-lgio-2.0;-lpangoft2-1.0;-lpangocairo-1.0;-lgdk_pixbuf-2.0;-lcairo;-lpango-1.0;-lfreetype;-lfontconfig;-lgobject-
>>> 2.0;-lglib-2.0;-lwxregexu-2.9;-lwxjpeg-2.9;-lwxpng-2.9;-lwxzlib-2.9;-ldl;-lm
>>>
>>> (note the last last that includes -lwxpng-2.9). I tried (using brute
>>> force) to exclude wxpng from the link command, but failed. Ideally
>>> wxlua should somehow check if the library is configured as "builtin"
>>> or "sys", but for now I just need to check if this is going to work
>
> Check what and from whom?
>
>>> for me, so, I'm fine with modifying it manually. I need to exclude
>>> libpng as it creates problems with systems libraries required by GTK
>>> on Linux.
>>>
>>> What is the way for me to tell wxlua *not* to include wxpng-2.9? Thank you.
>
> wxLua links to whatever libraries that wxWidgets was linked to. Please
> see the docs below and run the appropriate "wx-config" command to
> understand how your wxWidgets libs were built and where the values in
> wxWidgets_LIBRARIES come from.
>
> http://wxlua.sourceforge.net/docs/install.html#C2.5
>
> As I have mentioned before and as people on the Lua mailing explained
> recently (though not definitively enough) you cannot just link
> together random versions or builds of libraries together. For example,
> if you want to use the system png library then everything your app
> (wx.so) links to must have been built against that same lib. It is a
> recipe for disaster to try mix versions. It may work, but you should
> have no expectation that it should or will the next time you build it.
> The problem with using another random version/build of a png lib (for
> example) on Linux is that GTK will definitely be linked to the sys
> version and GTK cannot be easily (or maybe ever) be linked to
> staticly.
>
> Regards,
>      John
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] Segfaults in wxlua on Linux (when using "assert" or "return")

[John L. <jla...@gm...>]

On Mon, Mar 18, 2013 at 5:29 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> I'm using assert() to check some of the conditions in my code before I
> start the event loop and noticed that when the script exits after
> "require 'wx'", but before the main loop is started, it triggers
> segfault on Linux (tested on Fedora 18, but I saw the same thing on
> Ubuntu).

Well, I'm not sure there is much difference between what is happening
and what you're asking to happen by calling assert(), which is to
terminate the program violently. But, in any case, I don't get the
same result so I suspect something is wrong with your build. I would
review your build and clean and rebuild it after sorting out any
inconsistencies with multiple png libs or anything else like that.

I just tried the program "test.lua" using the lastest wxLua SVN using
wxLua's provided Lua5.1 in CentOS 6. (I just noticed that you have to
do "mv libwx.so wx.so", I will fix that)

-- ------------------------------------------------------
-- test.lua
local wx = require("wx")
--os.exit()
--assert(false)
--return
print("hello")
-- ------------------------------------------------------

Note that I'm in the build-2.9-wx_gtk2/lib/Debug dir and run $gdb
../../bin/Debug/lua. That could also be a problem, are you building
using one version/build of Lua then running with a different one?

-- THIS HAS os.exit() unremmed
(gdb) run test.lua
Starting program:
/home/john/wx/wx-svn/wx-svn/wx/build-2.9-wx_gtk2/bin/Debug/lua
test.lua
[Thread debugging using libthread_db enabled]
Program exited normally.

-- THIS HAS assert(false) unremmed
(gdb) run test.lua
Starting program:
/home/john/wx/wx-svn/wx-svn/wx/build-2.9-wx_gtk2/bin/Debug/lua
test.lua
[Thread debugging using libthread_db enabled]
/home/john/wx/wx-svn/wx-svn/wx/build-2.9-wx_gtk2/bin/Debug/lua:
test.lua:5: assertion failed!
stack traceback:
        [C]: in function 'assert'
        test.lua:5: in main chunk
        [C]: ?

Program exited with code 01.

-- THIS HAS return unremmed
(gdb) run test.lua
Starting program:
/home/john/wx/wx-svn/wx-svn/wx/build-2.9-wx_gtk2/bin/Debug/lua
test.lua
[Thread debugging using libthread_db enabled]
hello
Program exited normally.

-- THIS just lets it run through.
(gdb) run test.lua
Starting program:
/home/john/wx/wx-svn/wx-svn/wx/build-2.9-wx_gtk2/bin/Debug/lua
test.lua
[Thread debugging using libthread_db enabled]
hello
Program exited normally.
(gdb)

----------------------------------------------------------------------

Re: [wxlua-users] How to configure wxlua to *not* link wxpng library?

[John L. <jla...@gm...>]

On Mon, Mar 18, 2013 at 1:55 AM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> I ended up patching the makefile
> (luamodule/CMakeFiles/wxLuaModules.dir/link.txt), but would prefer
> something a bit more robust.

This is not a good idea.

> On Sun, Mar 17, 2013 at 9:58 AM, Paul K <pau...@ya...> wrote:
>> Hi John,
>>
>> I ran into an issue with configuring wxlua to use system libpng
>> library. I tried both --with-libpng=builtin and --with-libpng=sys, but
>> I get exactly the same result.

wxLua does not have switches "--with-libpng" are you talking about
building the wxWidgets library?

>> This discussion
>> (https://groups.google.com/forum/?fromgroups=#!topic/wx-users/2QWQD0qUVUc)
>> indicates that it's better to use a system library, but I can't

Yes, it nearly always is best to use the system libraries for such
basic libs (zlib, png, tiff, jpeg, and gtk).

Reread that thread, it explains exactly what your problem is and how
to fix it by using the system libs. Hint: don't specify --with-libpng
at all and last few lines of the output of configure tells you what
will be used. Don't forget to clean or preferably delete the old
wxWidgets build dir to be sure that you're getting what you think
you're getting.

>> configure wxlua to *not* link builtin library as can be see from this
>> output from cmake:
>>
>> -- * - wxWidgets_LIBRARIES         =
>> -L/home/paul/zbs/build/deps/lib;-pthread;;;/home/paul/zbs/build/deps/lib
>> /libwx_gtk2u_stc-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_aui-2.9.a;/home/paul/zbs/build/deps/lib
>> /libwx_baseu_net-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_html-2.9.a;/home/paul/zbs/build/deps/lib
>> /libwx_gtk2u_adv-2.9.a;/home/paul/zbs/build/deps/lib/libwx_gtk2u_core-2.9.a;/home/paul/zbs/build/deps/lib
>> /libwx_baseu-2.9.a;-lwxscintilla-2.9;-pthread;-lgthread-2.0;-lrt;-lX11;-lXxf86vm;-lgtk-x11-2.0;-lgdk-x11-2.0;-latk-
>> 1.0;-lgio-2.0;-lpangoft2-1.0;-lpangocairo-1.0;-lgdk_pixbuf-2.0;-lcairo;-lpango-1.0;-lfreetype;-lfontconfig;-lgobject-
>> 2.0;-lglib-2.0;-lwxregexu-2.9;-lwxjpeg-2.9;-lwxpng-2.9;-lwxzlib-2.9;-ldl;-lm
>>
>> (note the last last that includes -lwxpng-2.9). I tried (using brute
>> force) to exclude wxpng from the link command, but failed. Ideally
>> wxlua should somehow check if the library is configured as "builtin"
>> or "sys", but for now I just need to check if this is going to work

Check what and from whom?

>> for me, so, I'm fine with modifying it manually. I need to exclude
>> libpng as it creates problems with systems libraries required by GTK
>> on Linux.
>>
>> What is the way for me to tell wxlua *not* to include wxpng-2.9? Thank you.

wxLua links to whatever libraries that wxWidgets was linked to. Please
see the docs below and run the appropriate "wx-config" command to
understand how your wxWidgets libs were built and where the values in
wxWidgets_LIBRARIES come from.

http://wxlua.sourceforge.net/docs/install.html#C2.5

As I have mentioned before and as people on the Lua mailing explained
recently (though not definitively enough) you cannot just link
together random versions or builds of libraries together. For example,
if you want to use the system png library then everything your app
(wx.so) links to must have been built against that same lib. It is a
recipe for disaster to try mix versions. It may work, but you should
have no expectation that it should or will the next time you build it.
The problem with using another random version/build of a png lib (for
example) on Linux is that GTK will definitely be linked to the sys
version and GTK cannot be easily (or maybe ever) be linked to
staticly.

Regards,
     John

[wxlua-users] Segfaults in wxlua on Linux (when using "assert" or "return")

[Paul K <pau...@ya...>]

Hi John,

I'm using assert() to check some of the conditions in my code before I
start the event loop and noticed that when the script exits after
"require 'wx'", but before the main loop is started, it triggers
segfault on Linux (tested on Fedora 18, but I saw the same thing on
Ubuntu).

The script is as simple as one line with require 'wx'. Adding one more
line causes various segfaults that all seem to be originating from
wxLuaStateRefData::CloseLuaState; the results are shown below. I'd
appreciate any insight into what may be causing this or how to fix it.
Thank you.

Paul.

os.exit() -- no segfault

assert(false) -- segfault

#0  0x08055a4a in newkey ()
#1  0x0804ccb8 in lua_rawset ()
#2  0xb7177b12 in wxlua_lreg_createtable(lua_State*, void*, int, int)
()  from bin/linux/x86/libwx.so
#3  0xb7179861 in wxLuaStateRefData::ClearCallbacks() () from
bin/linux/x86/libwx.so
#4  0xb7179a37 in wxLuaStateRefData::CloseLuaState(bool) () from
bin/linux/x86/libwx.so
#5  0xb7179c32 in wxLuaState::Destroy() () from bin/linux/x86/libwx.so
#6  0xb70883e0 in wxLuaState::~wxLuaState() () from bin/linux/x86/libwx.so
#7  0x46c17f01 in __run_exit_handlers () from /lib/libc.so.6
#8  0x46c17f8d in exit () from /lib/libc.so.6
#9  0x46bff86d in __libc_start_main () from /lib/libc.so.6
#10 0x0804abb5 in _start ()

return -- segfault

#0  0x46c5ec06 in free () from /lib/libc.so.6
#1  0x08058c68 in l_alloc ()
#2  0x080513ab in luaM_realloc_ ()
#3  0x0805008f in luaF_freeproto ()
#4  0x080509b0 in sweeplist ()
#5  0x08050e3e in singlestep ()
#6  0x080511df in luaC_fullgc ()
#7  0x0804d1c8 in lua_gc ()
#8  0xb7143a70 in wxLuaStateRefData::CloseLuaState(bool) ()  from
bin/linux/x86/libwx.so
#9  0xb7143c32 in wxLuaState::Destroy() () from bin/linux/x86/libwx.so
#10 0xb70523e0 in wxLuaState::~wxLuaState() () from bin/linux/x86/libwx.so
#11 0x46c17f01 in __run_exit_handlers () from /lib/libc.so.6
#12 0x46c17f8d in exit () from /lib/libc.so.6
#13 0x46bff86d in __libc_start_main () from /lib/libc.so.6
#14 0x0804abb5 in _start ()

do nothing (the script ends not starting the event loop) -- segfault

*** glibc detected *** bin/linux/x86/lua: double free or corruption
(out): 0x46d987d8 ***

#0  0xb7704424 in __kernel_vsyscall ()
#1  0x46c14b7f in raise () from /lib/libc.so.6
#2  0x46c164d3 in abort () from /lib/libc.so.6
#3  0x46c54405 in __libc_message () from /lib/libc.so.6
#4  0x46c5bff9 in _int_free () from /lib/libc.so.6
#5  0x08058c68 in l_alloc ()
#6  0x080513ab in luaM_realloc_ ()
#7  0x0805006e in luaF_freeproto ()
#8  0x080509b0 in sweeplist ()
#9  0x08050e3e in singlestep ()
#10 0x080511df in luaC_fullgc ()
#11 0x0804d1c8 in lua_gc ()
#12 0xb70d5a70 in wxLuaStateRefData::CloseLuaState(bool) () from
bin/linux/x86/libwx.so
#13 0xb70d5c32 in wxLuaState::Destroy() () from bin/linux/x86/libwx.so
#14 0xb6fe43e0 in wxLuaState::~wxLuaState() () from bin/linux/x86/libwx.so
#15 0x46c17f01 in __run_exit_handlers () from /lib/libc.so.6
#16 0x46c17f8d in exit () from /lib/libc.so.6
#17 0x46bff86d in __libc_start_main () from /lib/libc.so.6
#18 0x0804abb5 in _start ()