From: Eli Zaretskii <eliz@gnu.org>
To: tom@tromey.com
Cc: emacs-devel@gnu.org
Subject: Re: 32-bit MinGW build with JIT
Date: Thu, 16 Aug 2018 20:35:26 +0300 [thread overview]
Message-ID: <83y3d6gqox.fsf@gnu.org> (raw)
In-Reply-To: <838t56iet0.fsf@gnu.org> (message from Eli Zaretskii on Thu, 16 Aug 2018 17:09:15 +0300)
> Date: Thu, 16 Aug 2018 17:09:15 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
>
> 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.
next prev parent reply other threads:[~2018-08-16 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 14:09 32-bit MinGW build with JIT Eli Zaretskii
2018-08-16 17:35 ` Eli Zaretskii [this message]
2018-08-18 9:14 ` Eli Zaretskii
2018-08-19 15:24 ` Tom Tromey
2018-08-19 15:37 ` Eli Zaretskii
2018-08-19 15:50 ` Tom Tromey
2018-08-19 16:15 ` Eli Zaretskii
2018-08-27 19:52 ` Ken Brown
2018-08-28 5:25 ` Eli Zaretskii
2018-08-28 13:12 ` Ken Brown
2018-08-28 16:58 ` Eli Zaretskii
2018-08-19 17:11 ` Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y3d6gqox.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).