From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Hook for script debugging
Date: Fri, 02 Oct 2009 10:35:53 +0200 [thread overview]
Message-ID: <87iqey9ora.fsf@gnu.org> (raw)
In-Reply-To: 87vdj48hmh.fsf@ossau.uklinux.net
Hello,
Neil Jerram <neil@ossau.uklinux.net> writes:
> I think it's inelegant to have to edit a script in order to debug it.
> If there is some generally useful system for debugging/introspection of
> a running Guile program - such as GDS, as I hope it will eventually
> become - it seems more efficient to be able to have a global switch for
> invoking that system - e.g. adding GUILE_BOOT_FORM to the environment -
> than to have to temporarily add the same invocation code to each program
> that you want to examine (and then remove it again when no longer
> needed).
Right, that’s a more compelling argument to me. That is, if such a
mechanism can help provide a standard way to debug a program via GDS,
then I’m all for it.
Thanks,
Ludo’.
prev parent reply other threads:[~2009-10-02 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 14:51 Hook for script debugging Neil Jerram
2009-09-26 21:06 ` Ludovic Courtès
2009-09-27 16:41 ` Neil Jerram
2009-10-02 8:35 ` Ludovic Courtès [this message]
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=87iqey9ora.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).