On 3/29/06, Francesco Montorsi <[EMAIL PROTECTED]> wrote:
> >> I've updated bakefiles but now, when I try to run wxluaedit I get a
> >> segmentation fault... (this with wx2.6.3 and with an up2date
> >> wxStedit...); other apps and samples I've tried work fine.
> >
> > Ok, I'll try to debug it, works ok in linux for me.
> I forgot to say that
> 1) I'm in linux, too
> 2) I'm using release, unicode builds (I'm messing with autopackages once
> again ;))
> I'll try soon with a debug build
If you still have problems see what gdb can say. I just retried it and
gdb says it exists cleanly. I even tried valgrind and it didn't find
any problems, though I can't say the same for gdk and glib, half a
dozen invalid reads and hundreds of unfreed memory blocks, totaling
1Mb. :(
Gdb does give me these about every 2 seconds though. I wonder who's
creating the threads? I don't think lua is? Maybe it's just from the
wxLuaEditor program which calls wxYield to fake running the wxLuaState
as a thread (it runs in the main thread).
[New Thread -1239192656 (LWP 16373)]
[Thread -1239192656 (LWP 16373) exited]
[New Thread -1239192656 (LWP 16376)]
[Thread -1239192656 (LWP 16376) exited]
> >>> 1) lua 5.1 does not have an "include" dir so I faked it by copying the
> >>> pertinent headers that we use into it.
> >> if you want to keep the header files in lua/src/ folder it's fine for me
> >> as it's not a problem for bakefiles ;)
> >
> > What about installing? I guess it'd be ok too since lua doesn't use
> > directories to nicely confine their headers anyway so it's just a
> > matter of fully specifying the include path.
> >
> > #include "lua.h" instead of "lua/lua.h"
> yes, exactly; changing the way headers are included there should be no
> problem at all...
Ok, then lets stick with having an "official" version of lua 5.1.
Would you mind removing the modules/lua/include dir files and
rebaking. I apologize about no doing it myself since I can't get a
compiled version of your bakefile to generate identical build files to
what you've got and until you get a chance I'd like to keep it
working. :)
> PS: I forgot to say that I removed the WXLUA_CODE symbol from compiler
> line as otherwise I get a redefinition error...
That was an mistake on my part, let's just leave it as is. This was
for some code I added to lua's lstate.c file to allow you to have a
function run whenever a coroutine is created and destroyed. By default
nothing happens since the handler is NULL. Someone added this #ifdef
and last night I was lazy and just put in #define WXLUA_CODE right in
the lstate.c file. I think it's just as well to run the code since it
checks for NULL so it's harmless and only gets run for coroutines. I'm
not sure why they thought it was better to #ifdef it off?
Thanks,
John Labenski
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Wxlua-users mailing list
Wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
