From: Mike Gran <spk121@yahoo.com>
To: Guile Devel <guile-devel@gnu.org>
Subject: debug and backtrace
Date: Fri, 11 Sep 2009 04:55:44 -0700 [thread overview]
Message-ID: <1252670144.24639.134.camel@localhost.localdomain> (raw)
Hi-
With the default behavior of 1.9.x, REPL debug and backtrace are broken.
Consider the following example run using 'guile --debug' and
(debug-enable 'backtrace).
With 1.8.5
--------------------------------------------------------
guile> (string-append "abc" (string-append "def" (string-append (error
"blammo"))))
Backtrace:
In standard input:
2: 0* [string-append "abc" ...
2: 1* [string-append "def" ...
2: 2* [string-append ...
2: 3* [error "blammo"]
standard input:2:58: In procedure error in expression (error "blammo"):
standard input:2:58: blammo
ABORT: (misc-error)
guile> (debug)
This is the Guile debugger -- for help, type `help'.
There are 4 frames on the stack.
Frame 3 at standard input:2:58
[error "blammo"]
debug> up
Frame 2 at standard input:2:43
[string-append ...
debug> up
Frame 1 at standard input:2:22
[string-append "def" ...
debug> up
Frame 0 at standard input:2:1
[string-append "abc" ...
--------------------------------------------------------
With 1.9.x
--------------------------------------------------------
scheme@(guile-user)> (string-append "abc" (string-append
"def" (string-append (error "blammo"))))
Backtrace:
In unknown file:
?: 0* [#<vm a0389b8> #<program a272300 at standard input:1:0 ()>]
?: 1* [error "blammo"]
ERROR: In procedure error:
ERROR: blammo
scheme@(guile-user)> (debug)
This is the Guile debugger -- for help, type `help'.
There are 2 frames on the stack.
Frame 1 at unknown source location
[error "blammo"]
debug> up
Frame 0 at unknown source location
[#<vm a0389b8> #<program a272300 at standard input:1:0 ()>]
--------------------------------------------------------
Thanks,
Mike
next reply other threads:[~2009-09-11 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 11:55 Mike Gran [this message]
2009-09-13 14:30 ` debug and backtrace Ludovic Courtès
2009-09-13 20:47 ` Neil Jerram
2009-09-16 19:31 ` Andy Wingo
2009-09-16 21:24 ` Neil Jerram
2009-09-17 12:24 ` Ludovic Courtès
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=1252670144.24639.134.camel@localhost.localdomain \
--to=spk121@yahoo.com \
--cc=guile-devel@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).