unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Derek Peschel <dpeschel@eskimo.com>
To: Neil Jerram <neiljerram@googlemail.com>
Cc: guile-devel@gnu.org
Subject: Re: Evaluating (exit) in the debugger
Date: Fri, 21 Nov 2008 13:14:04 -0800	[thread overview]
Message-ID: <20081121131404.A17225@eskimo.com> (raw)
In-Reply-To: <20081121015851.A14566@eskimo.com>; from dpeschel@eskimo.com on Fri, Nov 21, 2008 at 01:58:51AM -0800

On Fri, Nov 21, 2008 at 01:58:51AM -0800, Derek Peschel wrote:
> I also have to figure out why eval-handler is not getting an ordinary quit
> exception in test 1.

Sorry if this series of follow-ups is bad style -- I'm thinking this out
in public.  Maybe the documentation will be useful in some way.

My question was a useful clue that something was wrong.  Intuitively,
if the code being evaluated throws a quit exception, you'd expect eval-
handler to get the quit exception.  It does, _at the beginning_ before
its internal catch runs, whereas test 1 was looking inside the catch.

The correct change to eval-handler is quite minor:  just rethrow any quit
exceptins it gets, and do the rethrow before any of the error-anlysis code
takes over.  Then debug-handler gets the quit.  My last patch dealt with
that part of the sequence of events.  So the problem is fully solved and
I'll send out a new patch soon.

And thanks for your help.  The comment about 'continue got me to look more
closely at eval-handler.

-- Derek




  reply	other threads:[~2008-11-21 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20  0:53 Evaluating (exit) in the debugger Derek Peschel
2008-11-21  0:09 ` Neil Jerram
2008-11-21  0:48   ` Derek Peschel
2008-11-21  9:58     ` Derek Peschel
2008-11-21 21:14       ` Derek Peschel [this message]
2008-11-23 22:24     ` 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=20081121131404.A17225@eskimo.com \
    --to=dpeschel@eskimo.com \
    --cc=guile-devel@gnu.org \
    --cc=neiljerram@googlemail.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).