unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Backtraces in Guile 2.0
Date: Tue, 22 Feb 2011 09:20:25 +0100	[thread overview]
Message-ID: <m34o7wxyye.fsf@unquote.localdomain> (raw)
In-Reply-To: <467344.39605.qm@web37901.mail.mud.yahoo.com> (Mike Gran's message of "Mon, 21 Feb 2011 19:23:03 -0800 (PST)")

Hi Mike,

On Tue 22 Feb 2011 04:23, Mike Gran <spk121@yahoo.com> writes:

>   (symbol->string "STRING")
>
>    In module/ice-9/boot-9.scm:
>    1917: 3 [save-module-excursion #<procedure 14f3180 at module/ice-9/boot-9.scm:3341:3 ()>]
>    3348: 2 [#<procedure 14f3180 at module/ice-9/boot-9.scm:3341:3 ()>]
>    In unknown file:
>       ?: 1 [load-compiled/vm "/home/mike/.cache/guile/ccache/2.0-LE-8-2.0/home/mike/Documents/code/guile_backtrace/symbol1.scm.go"]
>       ?: 0 [symbol->string "STRING"]

Here, there is no procedure in the call chain that has source
annotations corresponding to symbol1.scm.  Though, it does seem to me
that the load-compiled/vm line is unnecessary; instead we should load up
the .go into a thunk, and run that thunk without recursing through the
load-compiled/vm primitive.

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.

Regards,

Andy
-- 
http://wingolog.org/



  parent reply	other threads:[~2011-02-22  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22  3:23 Backtraces in Guile 2.0 Mike Gran
2011-02-22  7:44 ` Klaus Schilling
2011-02-22  8:20 ` Andy Wingo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-22 17:53 Mike Gran
2011-02-22 19:13 ` Andy Wingo
2011-02-22 19:44   ` Linas Vepstas
2011-02-22 19:55 Mike Gran

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=m34o7wxyye.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-user@gnu.org \
    --cc=spk121@yahoo.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).