From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: debug and backtrace
Date: Sun, 13 Sep 2009 21:47:50 +0100 [thread overview]
Message-ID: <87my4y7ert.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <87y6oilxwx.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun\, 13 Sep 2009 16\:30\:38 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Hello!
>
> Mike Gran <spk121@yahoo.com> writes:
>
>> With the default behavior of 1.9.x, REPL debug and backtrace are broken.
>
> Indeed, it looks like the VM frames are ignored.
I've just hit this too. So here's another example, just in case it's
useful.
Given a file testcar.scm that contains
((lambda _
(car 1)))
1.8.x guile --debug -s testcar.scm gives a useful backtrace:
Backtrace:
In unknown file:
?: 0* [primitive-load "testcar.scm"]
In testcar.scm:
2: {1}* [#<procedure #f _>]
3: 2 [car {1}]
testcar.scm:3:4: In procedure car in expression (car 1):
testcar.scm:3:4: Wrong type (expecting pair): 1
But current (approximately speaking) Git master doesn't:
Backtrace:
In unknown file:
?: 0* [dynamic-wind #<program 9817a00 at ice-9/boot-9.scm:1771:18 ()> ...]
?: {1}* [with-fluid* #<fluid 9> #f #<program 98179a0 at ice-9/boot-9.scm:935:4 ()>]
?: 2* [load-compiled/vm "/home/neil/.cache/guile/ccache/1.9-0.D-LE-4/home/neil/SW/Guile/testcar.scm.go"]
ERROR: In procedure vm-debug-engine:
ERROR: Wrong type argument in position 1 (expecting pair): 1
Out of interest, is this something that has worked with the VM in the
past, and has somehow got broken? Or is it something that hasn't been
implemented for the VM yet? (I believe it's the former, but I'm not
sure.)
Regards,
Neil
next prev parent reply other threads:[~2009-09-13 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 11:55 debug and backtrace Mike Gran
2009-09-13 14:30 ` Ludovic Courtès
2009-09-13 20:47 ` Neil Jerram [this message]
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=87my4y7ert.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@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).