From: Matt Wette <matt.wette@gmail.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-user@gnu.org
Subject: Re: Stack traces
Date: Wed, 15 Feb 2017 17:10:41 -0800 [thread overview]
Message-ID: <F998501E-0D72-4AB8-ACF8-67F6A77780F7@gmail.com> (raw)
In-Reply-To: <87mvdn4gam.fsf@dustycloud.org>
> On Feb 15, 2017, at 7:36 AM, Christopher Allan Webber <cwebber@dustycloud.org> wrote:
>
> One thing that we see requested a lot is how to do the equivalent of:
>
> import pdb
> pdb.set_trace()
>
> in python, just dumping something to "trigger" the debugger somewhere.
> I seem to remember getting some arcane code to do something similar, but
> maybe we can just have a simple invocation that people could put
> anywhere. (Amirouche has been raising this one also I think.)
>
^^^This is exactly what I yearn for. I asked about this before and got the following hint, but could not get anything to work.
(use-modules (system repl repl))
(Use-modules (system repl debug))
...
(start-repl #:debug (make-debug (stack->vector (make-stack #t)) 0 "trap!" #t))
next prev parent reply other threads:[~2017-02-16 1:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.52572.1487077879.22737.guile-user@gnu.org>
2017-02-14 17:24 ` guile-user Digest, Vol 171, Issue 14 Cecil McGregor
2017-02-14 19:19 ` Christopher Allan Webber
2017-02-14 22:00 ` Amirouche
2017-02-14 22:16 ` Stack traces Ludovic Courtès
2017-02-15 15:36 ` Christopher Allan Webber
2017-02-16 1:10 ` Matt Wette [this message]
2017-02-18 0:13 ` Matt Wette
2017-02-18 15:50 ` Amirouche
2017-02-18 15:53 ` Amirouche
2017-02-18 16:58 ` Matt Wette
2017-02-18 19:59 ` Amirouche
2017-02-18 20:31 ` Matt Wette
2017-02-27 20:23 ` Andy Wingo
2017-02-27 20:40 ` Amirouche
2017-05-18 13:38 ` Christopher Allan Webber
2017-05-19 3:05 ` Matt Wette
2017-05-19 9:17 ` Andy Wingo
2017-06-10 9:58 ` Catonano
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=F998501E-0D72-4AB8-ACF8-67F6A77780F7@gmail.com \
--to=matt.wette@gmail.com \
--cc=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
--cc=ludo@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).