[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Stack traces
From: |
Matt Wette |
Subject: |
Re: Stack traces |
Date: |
Wed, 15 Feb 2017 17:10:41 -0800 |
> On Feb 15, 2017, at 7:36 AM, Christopher Allan Webber <address@hidden> 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))
- Re: guile-user Digest, Vol 171, Issue 14, Cecil McGregor, 2017/02/14
- Re: guile-user Digest, Vol 171, Issue 14, Christopher Allan Webber, 2017/02/14
- Re: guile-user Digest, Vol 171, Issue 14, Amirouche, 2017/02/14
- Stack traces, Ludovic Courtès, 2017/02/14
- Re: Stack traces, Christopher Allan Webber, 2017/02/15
- Re: Stack traces,
Matt Wette <=
- Re: Stack traces, Matt Wette, 2017/02/17
- Re: Stack traces, Amirouche, 2017/02/18
- Re: Stack traces, Amirouche, 2017/02/18
- Re: Stack traces, Matt Wette, 2017/02/18
- Re: Stack traces, Amirouche, 2017/02/18
- Re: Stack traces, Matt Wette, 2017/02/18
- Re: Stack traces, Andy Wingo, 2017/02/27
- Re: Stack traces, Amirouche, 2017/02/27