From: Christopher Allan Webber <cwebber@dustycloud.org>
To: 23435-done@debbugs.gnu.org
Subject: bug#23435: The solution to the mysterious SIGABRT
Date: Tue, 03 May 2016 20:24:09 -0500 [thread overview]
Message-ID: <87mvo6y5s6.fsf@dustycloud.org> (raw)
In-Reply-To: <87r3diyjca.fsf@dustycloud.org>
So with some help from Andy Wingo (thanks Andy!) I figured out what to
do. What happened is that when code in the resumed delimited
continuation threw an error, it attempted to find the original catch's
prompt, which had disappeared. Remember that I had a prompt in a
prompt, so the outer prompt's catch had gone away. The trick was to put
a catch around the inner prompt as well, repeating the same handlers
given to the outer prompt.
Not sure how coherent that is, but this fixed it. Thanks, Andy!
prev parent reply other threads:[~2016-05-04 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 20:31 bug#23435: Mysterious SIGABRT Christopher Allan Webber
2016-05-04 1:24 ` Christopher Allan Webber [this message]
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=87mvo6y5s6.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=23435-done@debbugs.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).