From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: 74269@debbugs.gnu.org
Cc: Ekaitz Zarraga <ekaitz@elenq.tech>
Subject: bug#74269: [PATCH] doc: Document GUILE_JIT_PAUSE_WHEN_STOPPING
Date: Fri, 8 Nov 2024 23:41:49 +0100 [thread overview]
Message-ID: <20241108224200.32164-1-ekaitz@elenq.tech> (raw)
* doc/ref/guile-invoke.texi: Add GUILE_JIT_PAUSE_WHEN_STOPPING
---
doc/ref/guile-invoke.texi | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/doc/ref/guile-invoke.texi b/doc/ref/guile-invoke.texi
index 7ceef0bb5..c837598b8 100644
--- a/doc/ref/guile-invoke.texi
+++ b/doc/ref/guile-invoke.texi
@@ -453,6 +453,18 @@ integer indicating the maximum number of functions to JIT-compile. By
bisecting over the value of @env{GUILE_JIT_STOP_AFTER}, you can pinpoint
the precise function that is being miscompiled.
+@item GUILE_JIT_PAUSE_WHEN_STOPPING
+@vindex GUILE_JIT_PAUSE_WHEN_STOPPING
+Debugging the JIT compiler sometimes requires analysing the running
+process. Setting @env{GUILE_JIT_PAUSE_WHEN_STOPPING} will pause the
+process when the JIT stops to let you connect a debugger to it and will
+print something along these lines:
+@example
+stopping automatic JIT compilation, as requested
+sleeping for 30s; to debug:
+ gdb -p 133646
+@end example
+
@end table
@c Local Variables:
--
2.46.0
reply other threads:[~2024-11-08 22:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241108224200.32164-1-ekaitz@elenq.tech \
--to=ekaitz@elenq.tech \
--cc=74269@debbugs.gnu.org \
/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.
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).