Re: [LuaJIT] Backtracing in GDB

[Alex <initrd.gz@...>]

On Mon, Apr 23, 2012 at 8:50 PM, Daurnimator <quae@daurnimator.com> wrote:

On 24 April 2012 11:43, Alex <initrd.gz@gmail.com> wrote:
> No, the program makes heavy use of FFI and other LuaJIT features.
>

How about with the jit compiler off?

Unfortunately, the same issue occurs.

On Mon, Apr 23, 2012 at 8:53 PM, James McKaskill <james@foobar.co.nz> wrote:

On Mon, Apr 23, 2012 at 21:43, Alex <initrd.gz@gmail.com> wrote:
> No, the program makes heavy use of FFI and other LuaJIT features.

Well that may or may not be an issue. For the FFI you can try
https://github.com/jmckaskill/luaffi, but YMMV as its still missing a
few features (If you do give that a try and find something missing, I
would greatly appreciate a bug report). What other LuaJIT features are
you dependent on?

PS: The reason I wrote luaffi in the first place was to debug some FFI
code, because debugging jit'ed code was kind of painful.

-- James

Hm, it would require some work, especially for checking pointers versus ffi.C.NULL instead of nil. Also, I think my mingw installation is messed up because the makefile calls uname, which crashes for some reason.