unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: bug-guile@gnu.org
Subject: Re: Problem with apply-frame trap in 1.6 and 1.7
Date: Thu, 04 Nov 2004 16:57:57 +0100	[thread overview]
Message-ID: <ljbredppx6.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <41892436.3030401@ossau.uklinux.net> (Neil Jerram's message of "Wed, 03 Nov 2004 18:32:22 +0000")

Neil Jerram <neil@ossau.uklinux.net> writes:

> Working on breakpoints for 1.6.x, I just discovered that the
> following ENTER_APPLY trap code in eval.c goes into a tight busy loop
> if (debug-enable 'trace) and (trap-set! apply-frame-handler non-#f).
>
>   if (CHECK_APPLY && SCM_TRAPS_P)\
>     if (SCM_APPLY_FRAME_P || (SCM_TRACE_P && PROCTRACEP (proc)))\
>
> This is because PROCTRACEP uses scm_procedure_property, which itself
> uses apply if proc is not a closure.

Hmm, I can't find the place where scm_procedure_property calls apply.
Could you give me a hint?  Hopefully, there is some misunderstanding
on your part so that we can avoid making subrs untraceable.  (Which is
what your proposed change does, right?)


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


  reply	other threads:[~2004-11-04 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 18:32 Problem with apply-frame trap in 1.6 and 1.7 Neil Jerram
2004-11-04 15:57 ` Marius Vollmer [this message]
2004-11-04 20:58   ` Neil Jerram
2004-12-15 17:06     ` Marius Vollmer
2004-12-15 17:12       ` Marius Vollmer
2004-12-15 17:29         ` Neil Jerram
2004-12-17  0:07           ` Neil Jerram
2004-12-17 11:20             ` Marius Vollmer

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=ljbredppx6.fsf@troy.dt.e-technik.uni-dortmund.de \
    --to=marius.vollmer@uni-dortmund.de \
    --cc=bug-guile@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).