From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Let's Talk About Backtraces and Stacks
Date: Thu, 17 Jan 2013 16:34:57 +0100 [thread overview]
Message-ID: <87zk07bz6m.fsf@pobox.com> (raw)
In-Reply-To: <CA+U71=NatJ3tgwaQgOGamVULpwx6+Z+9QSS8iWR2jicSFF5SGg@mail.gmail.com> (Noah Lavine's message of "Wed, 25 Apr 2012 10:49:51 -0400")
Hi :)
On Wed 25 Apr 2012 16:49, Noah Lavine <noah.b.lavine@gmail.com> writes:
> It seems to me that it's best for the ribcage to be part of the Scheme
> stack.
I'm pretty hesitant to do this; it penalizes procedure calls.
What first writing a prototype that uses the VM trap interface? You can
use `trap-calls-in-dynamic-extent'. The apply-handler will be called
for both tail and non-tail applications. See `(system vm trace)' for a
use example. Then you can figure out how to wire its information into
the backtrace at the REPL.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-01-17 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 14:49 Let's Talk About Backtraces and Stacks Noah Lavine
2013-01-17 15:34 ` Andy Wingo [this message]
2013-01-22 12:46 ` 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=87zk07bz6m.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.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).