Le jeu. 24 oct. 2019 à 01:48, Christopher Lam
a écrit :
[...]
> Not sure how much knowledge of debugger is required, all I want to do is to
> dump local variables at the breakpoint.
For records there is (set-record-type-printer! type proc):
https://www.gnu.org/software/guile/manual/html_nod
Agree it'll be a major aid to decreasing the learning curve. For now the
only way to analyse a variable in a script is to (pk) it, which is annoying
when it's a record/alist etc. Need to refine the pk several times or write
a custom printer.
Not sure how much knowledge of debugger is required, all
On 10/19/19 12:04 PM, Christopher Howard wrote:
Below is something I played with years ago. I'm not sure kill-opt is
up to date. Try with
> (load "jtd.scm")
> (foo)
[1]> ,loc
The code seems to evaluate fine, but does not produce useful results:
```
scheme@(guile-user)> ,use (po
> Below is something I played with years ago. I'm not sure kill-opt is
> up to date. Try with
>
>
> > (load "jtd.scm")
> > (foo)
> [1]> ,loc
The code seems to evaluate fine, but does not produce useful results:
```
scheme@(guile-user)> ,use (potluck jtd)
scheme@(guile-user)> (foo)
sche
Below is something I played with years ago. I'm not sure kill-opt is up to
date. Try with
> (load "jtd.scm")
> (foo)
[1]> ,loc
;; potluck/jtd - jump to debugger, detour to debugger
;;(define-module (potluck jtd) #:export (kill-opt trap-here foo))
(use-modules (system repl repl))
"Thompson, David" writes:
> On Fri, Oct 18, 2019 at 8:40 AM Matt Wette 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))
>
> Define dump-into-debugging-repl as
>
> (start-repl #:debug (make-debug (stack->vector (make-stack #t)) 0
> "trap!" #t))
>
> But as for getting access to locals I don't know if there is a
> solution. I have worked on removing slot sharing in the CPS
> processing
> but it's not working an
On Fri, Oct 18, 2019 at 8:40 AM Matt Wette 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))
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 qui
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.
I know from 6.26.3.2
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.
I know from 6.26.3.2
Hi Everyone,
Can someone point me to a good tutorial on debugging a script
interactively with guile? I've been poking around on the web for
something that gives me a good feel for the basics but no such luck.
Not sure it it exists but I figured best to ask here. I keep getting
hits that point me
12 matches
Mail list logo
