On Mon, Nov 24, 2008 at 11:23 AM, Raúl Huertas <[EMAIL PROTECTED]> wrote:
> Here is more info with lua builded for debug:
>
> (idb) file dist/Release/IntelSDK-Linux-x86/luaexample
...
> Program received signal SIGSEGV
> free () in /lib/tls/i686/cmov/libc-2.7.so
> (idb) bt
> #0 0xb7cdc4ac in free () in /lib/tls/i686/cmov/libc-2.7.so
> #1 0x08060ab2 in l_alloc (ud=0x8054d7f, ptr=0x0, osize=3077778016,
> nsize=28) at lauxlib.c:631
> #2 0x08054d7f in luaM_realloc_ (L=0x8243d38, block=0x80aa008,
> osize=134914056, nsize=134593111) at lmem.c:79
> #3 0x0805ba57 in luaH_free (L=0x0, t=0x8243d38) at ltable.c:376
> #4 0x080549be in luaC_freeall (L=0x0) at lgc.c:487
> #5 0x0805a6d4 in lua_close (L=0xb7db7ff4) at lstate.c:212
> #6 0x08049d5a in main () in
> /home/raulhuertas/Documentos/Proyectos/LuaExample/dist/Release/IntelSDK-Linux-x86/luaexample
>
> I will now compile wxlua for debug
Let me know the result of that. The above doesn't seem to show that
wxLua is misbehaving, but on the other hand Lua itself shouldn't have
problems like this nor should libc as you mention in your last post.
You can also try running $ldd luaexample and $ldd wx.so to make sure
that both your program and the wxLua lib are linked to the same Lua
lib.
By the way, on Linux you might as well always compile in debug mode,
unless you're going to distribute your program or actually require
speed.
Regards,
John
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
wxlua-users mailing list
wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
