From: "Thompson, David" <dthompson2@worcester.edu>
To: Matt Wette <matt.wette@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Interactive Debugging
Date: Fri, 18 Oct 2019 09:18:18 -0400 [thread overview]
Message-ID: <CAJ=RwfaibyyaEFmJctL5Xjc_0PU+hCdR88FLGYYaSLYjMjXAug@mail.gmail.com> (raw)
In-Reply-To: <b85e8069-3f0c-7dd1-d4a1-8fa819c442aa@gmail.com>
On Fri, Oct 18, 2019 at 8:40 AM Matt Wette <matt.wette@gmail.com> wrote:
>
> On 10/17/19 9:39 PM, Christopher Howard wrote:
> > Hi, it seems like with the flexibility of Guile, I should be able to do
> > something like this:
> > ```(define (foo) (let ((a 1) (b 2) (c 3)) (jump-into-
> > debugging-repl)))```
> > And have access to a, b, and c and their values. But I'm not quite
> > figuring out how to this.
> >
>
> Define dump-into-debugging-repl as
>
> (start-repl #:debug (make-debug (stack->vector (make-stack #t)) 0
> "trap!" #t))
I think something like this should be shipped in the (system repl
debug) module. I'm used to quick and easy access to a debugger in
other languages, such as Ruby, and having to wrap your head around the
REPL, debug, and stack code is too much to ask of any new Guiler.
Would a patch like this appeal to the maintainers?
- Dave
next prev parent reply other threads:[~2019-10-18 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 4:39 Interactive Debugging Christopher Howard
2019-10-18 12:39 ` Matt Wette
2019-10-18 13:18 ` Thompson, David [this message]
2019-10-18 21:21 ` Mark H Weaver
2019-10-19 14:42 ` Matt Wette
2019-10-23 23:48 ` Christopher Lam
2019-10-24 9:22 ` Amirouche Boubekki
[not found] <mailman.75.1571500806.2224.guile-user@gnu.org>
2019-10-19 19:04 ` Christopher Howard
2019-10-19 19:09 ` Matt Wette
[not found] <mailman.2435.1571402405.9712.guile-user@gnu.org>
2019-10-18 13:38 ` Christopher Howard
-- strict thread matches above, loose matches on Subject: below --
2019-10-18 4:37 Christopher Howard
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='CAJ=RwfaibyyaEFmJctL5Xjc_0PU+hCdR88FLGYYaSLYjMjXAug@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.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.
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).