2017-05-18 15:38 GMT+02:00 Christopher Allan Webber
:
> Amirouche writes:
>
> > Le 27/02/2017 à 21:23, Andy Wingo a écrit :
> >> On Sat 18 Feb 2017 20:59, Amirouche writes:
> >>
> >>> How do you access variables in the REPL?
> >> ,locals
> >>
>
On Thu 18 May 2017 15:38, Christopher Allan Webber
writes:
> I frequently find that ,locals does not display much information... it
> seems to be a toss-up whether the variables I need will be contained
> in it, so I've reduced the amount I use the actual debugger system
> On May 18, 2017, at 6:38 AM, Christopher Allan Webber
> wrote:
>
> Amirouche writes:
>
>> Le 27/02/2017 à 21:23, Andy Wingo a écrit :
>>> On Sat 18 Feb 2017 20:59, Amirouche writes:
>>>
How do you access variables in the REPL?
>>>
Amirouche writes:
> Le 27/02/2017 à 21:23, Andy Wingo a écrit :
>> On Sat 18 Feb 2017 20:59, Amirouche writes:
>>
>>> How do you access variables in the REPL?
>> ,locals
>>
>> Andy
> It doesn't display something that I can use.
(Returning to this few-months-old
Le 27/02/2017 à 21:23, Andy Wingo a écrit :
On Sat 18 Feb 2017 20:59, Amirouche writes:
How do you access variables in the REPL?
,locals
Andy
It doesn't display something that I can use.
> On Feb 18, 2017, at 11:59 AM, Amirouche wrote:
> How do you access variables in the REPL?
To be determined. Just starting, and I’m guessing this part is going to be
nontrivial: some may optimized away, some (e.g., those set!) are boxed, etc.
Le 18/02/2017 à 17:58, Matt Wette a écrit :
On Feb 18, 2017, at 7:53 AM, Amirouche wrote:
Le 18/02/2017 à 16:50, Amirouche a écrit :
Le 18/02/2017 à 01:13, Matt Wette a écrit :
(use-modules (system repl repl))
(use-modules (system repl debug))
(define-syntax-rule
Le 18/02/2017 à 16:50, Amirouche a écrit :
Le 18/02/2017 à 01:13, Matt Wette a écrit :
(use-modules (system repl repl))
(use-modules (system repl debug))
(define-syntax-rule (trap-here)
(start-repl
#:debug (make-debug (stack->vector (make-stack #t)) 0 "trap!" #t)))
(define (foo)
Le 18/02/2017 à 01:13, Matt Wette a écrit :
(use-modules (system repl repl))
(use-modules (system repl debug))
(define-syntax-rule (trap-here)
(start-repl
#:debug (make-debug (stack->vector (make-stack #t)) 0 "trap!" #t)))
(define (foo)
(let iter ((sum 0) (vals '(1 2 3 5 8 2)))
> On Feb 15, 2017, at 7:36 AM, Christopher Allan Webber
> 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
> On Feb 15, 2017, at 7:36 AM, Christopher Allan Webber
> 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
Ludovic Courtès writes:
> Hello,
>
> Cecil McGregor skribis:
>
>> My first problem lies in the lack of a decent debugger.
>> (I can hear the screams of more enlightened Guilers
>> already!) The stack traces seldom provide filenames
>> and line numbers to hint where a
12 matches
Mail list logo