From: Christopher Allan Webber <cwebber@dustycloud.org>
To: 25300@debbugs.gnu.org
Subject: bug#25300: Trap infrastructure broken in Guile 2.2?
Date: Fri, 30 Dec 2016 11:56:33 -0600 [thread overview]
Message-ID: <874m1lgv1q.fsf@dustycloud.org> (raw)
Guile 2.0.13:
scheme@(guile-user)> (define (foo n)
(if (= n 0)
'done
(foo (1- n))))
scheme@(guile-user)> ,tracepoint foo
Trap 0: Tracepoint at #<procedure foo (n)>.
scheme@(guile-user)> (foo 5)
Trap 0: (foo 5)
Trap 0: | (foo 4)
Trap 0: | | (foo 3)
Trap 0: | | | (foo 2)
Trap 0: | | | | (foo 1)
Trap 0: | | | | | (foo 0)
Trap 0: | | | | | done
Trap 0: | | | | done
Trap 0: | | | done
Trap 0: | | done
Trap 0: | done
Trap 0: done
$2 = done
scheme@(guile-user)>
Guile 2.1.5 (via guile-next in guix):
scheme@(guile-user)> (define (foo n)
(if (= n 0)
'done
(foo (1- n))))
... ... ... scheme@(guile-user)>
scheme@(guile-user)> ,tracepoint foo
Trap 0: Tracepoint at #<procedure foo (n)>.
scheme@(guile-user)> (foo 30)
$1 = done
Likewise, ,break and etc do not work for me.
next reply other threads:[~2016-12-30 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 17:56 Christopher Allan Webber [this message]
2017-03-01 15:09 ` bug#25300: Trap infrastructure broken in Guile 2.2? Andy Wingo
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=874m1lgv1q.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=25300@debbugs.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).