From: Mike Gran <spk121@yahoo.com>
To: Andy Wingo <wingo@pobox.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Backtraces in Guile 2.0
Date: Tue, 22 Feb 2011 09:53:56 -0800 (PST) [thread overview]
Message-ID: <773019.4427.qm@web37908.mail.mud.yahoo.com> (raw)
> From:Andy Wingo <wingo@pobox.com>
> In any case it seems that symbol1.scm.go tail-calls symbol->string, so
> we are left without source info. Bummer. We could improve this by
> keeping a ring buffer of previous frames, like JRM suggests in
> http://funcall.blogspot.com/2009/05/you-knew-id-say-something-part-iv.html.
So, the specific line on which the error occurred will always read
"in unknown file" because source data is a property of procedures. And,
when procedure A tail-calls procedure B, the backtrace may only
display the information of the procedure A. Right?
Thus, if I understand correctly, the closest I can get to getting source
info for this trivial case would be to change the script to
(symbol->string "HELLO")
#t
Adding a #t so it can't be tail-called. Then I get
In unknown file:
?: 2 [load-compiled/vm "/home/Mike/.cache/guile/ccache/2.0-LE-4-2.0/home/Mike/tmp.scm.go"]
In /home/Mike/tmp.scm:
1: 1 [#<procedure 13fa550 ()>]
In unknown file:
?: 0 [symbol->string "STRING"]
ERROR: In procedure symbol->string:
Thanks,
-Mike
next reply other threads:[~2011-02-22 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 17:53 Mike Gran [this message]
2011-02-22 19:13 ` Backtraces in Guile 2.0 Andy Wingo
2011-02-22 19:44 ` Linas Vepstas
-- strict thread matches above, loose matches on Subject: below --
2011-02-22 19:55 Mike Gran
2011-02-22 3:23 Mike Gran
2011-02-22 7:44 ` Klaus Schilling
2011-02-22 8:20 ` 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=773019.4427.qm@web37908.mail.mud.yahoo.com \
--to=spk121@yahoo.com \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/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).