unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: frames / stacks / source?  was Re: coverage/profiling
Date: Wed, 10 Jan 2007 08:46:29 +0000	[thread overview]
Message-ID: <87mz4rfevu.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <45A41BBD.1080906@xs4all.nl> (Han-Wen Nienhuys's message of "Tue, 09 Jan 2007 23:48:29 +0100")

Han-Wen Nienhuys <hanwen@xs4all.nl> writes:

> Neil Jerram escreveu:
>> Do you think you need to do this in C?  (You might do, for reasonable
>> performance - I genuinely don't know yet.)  The evaluator already has
>> hooks (see "Evaluator trap options" in the manual) that allow you to
>> call out to arbitrary Scheme code at the entry and exit of every
>> frame.
>
> [hanwen@haring info]$ guile
> guile> (trap-enable 'enter-frame-handler)
> throw from within critical section.
> Abortado
> [hanwen@haring info]$ 

Takes effect quickly, doesn't it? :-)

What you need is something more like this:

(trap-set! enter-frame-handler
  (lambda (key continuation . args)
    ...))
(trap-enable 'enter-frame)

And it's important to do them in this order.

Regards,
     Neil



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2007-01-10  8:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 18:19 coverage/profiling Han-Wen Nienhuys
2007-01-08 23:48 ` frames / stacks / source? was coverage/profiling Han-Wen Nienhuys
2007-01-09  9:10   ` Ludovic Courtès
2007-01-09 13:32     ` Han-Wen Nienhuys
2007-01-09 14:07     ` Andy Wingo
2007-01-09 22:05   ` Kevin Ryde
2007-01-09 22:15   ` Neil Jerram
2007-01-09 22:45     ` Han-Wen Nienhuys
2007-01-09 22:48     ` Han-Wen Nienhuys
2007-01-10  8:46       ` Neil Jerram [this message]
2007-01-10 12:59         ` Han-Wen Nienhuys
2007-01-10  9:16       ` Ludovic Courtès
2007-01-10 11:44         ` Han-Wen Nienhuys
2007-01-17 22:57           ` Kevin Ryde
2007-01-10 15:43     ` Han-Wen Nienhuys
2007-01-11  8:46       ` Ludovic Courtès
2007-01-11 10:19         ` Han-Wen Nienhuys
2007-01-11 15:57           ` Ludovic Courtès
2007-01-14  0:36     ` Neil Jerram
2007-01-18 23:15       ` Kevin Ryde
2007-01-27 18:12         ` Neil Jerram

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=87mz4rfevu.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --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).