[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 32-bit MinGW build with JIT
From: |
Eli Zaretskii |
Subject: |
Re: 32-bit MinGW build with JIT |
Date: |
Thu, 16 Aug 2018 20:35:26 +0300 |
> Date: Thu, 16 Aug 2018 17:09:15 +0300
> From: Eli Zaretskii <address@hidden>
> Cc: address@hidden
>
> Anyway, what I wanted to tell is that as of now, it is very hard to
> debug these problems. All the libjit types are "incomplete" as far as
> GDB is concerned, there are no facilities to display libjit types and
> values in human-readable form, C-level backtraces show ?? when a JIT
> compiled function is called, etc. I didn't yet succeed in
> establishing whether the invalid Lisp arguments for Ffuncall are
> already invalid when we compile the function, or get corrupted as part
> of compilation.
>
> I think we need to upgrade our debugging facilities, including adding
> commands to .gdbinit, as part of working on this branch.
Oh, and one more thing: I think we need a Lisp variable to disable JIT
even if it has been compiled in. This should be important for
debugging and testing, if nothing else.
- 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/16
- Re: 32-bit MinGW build with JIT,
Eli Zaretskii <=
- Re: 32-bit MinGW build with JIT, Tom Tromey, 2018/08/19
- Re: 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/19
- Re: 32-bit MinGW build with JIT, Tom Tromey, 2018/08/19
- Re: 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/19
- Re: 32-bit MinGW build with JIT, Ken Brown, 2018/08/27
- Re: 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/28
- Re: 32-bit MinGW build with JIT, Ken Brown, 2018/08/28
- Re: 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/28
- Re: 32-bit MinGW build with JIT, Paul Eggert, 2018/08/19