From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org, Ian Price <ianprice90@googlemail.com>,
guile-devel <guile-devel@gnu.org>
Subject: Re: exit & dynamic wind
Date: Wed, 30 Mar 2011 12:45:58 +0200 [thread overview]
Message-ID: <m3ipv051jt.fsf@unquote.localdomain> (raw)
In-Reply-To: <m3pqpff8t3.fsf@unquote.localdomain> (Andy Wingo's message of "Fri, 25 Mar 2011 17:45:28 +0100")
Hello!
On Fri 25 Mar 2011 17:45, Andy Wingo <wingo@pobox.com> writes:
> On Fri 25 Mar 2011 02:52, Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> Andy Wingo <wingo@pobox.com> writes:
>>
>>> I have pushed something that causes the stack to be unwound before
>>> exiting.
>>
>> | GEN guile-procedures.texi
>> | guile: uncaught throw to wrong-type-arg: (#f Wrong type (expecting ~A): ~S (exact integer (#t #<catch-closure 9916c10> #<catch-closure 9916be0>)) ((#t #<catch-closure 9916c10> #<catch-closure 9916be0>)))
This, it turns out, was something more pernicious, fixed in
572eef50c2d902d34427945dd504ba03af666e48.
>> Reverting ecba00af6501e082b86c8f2f7730081c733509d7 fixes this again.
>
> I reverted that patch, it was poorly considered. (Before, that code
> would print a backtrace in some cases, which was a good thing.)
I have reapplied it with modifications: now, the exception and backtrace
are printed before unwinding. The exit() happens after unwinding.
Happy hacking!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-30 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 13:26 exit & dynamic wind Ian Price
2011-03-24 19:23 ` Andy Wingo
2011-03-25 1:52 ` Neil Jerram
2011-03-25 16:45 ` Andy Wingo
2011-03-30 10:45 ` Andy Wingo [this message]
2011-03-30 18:31 ` Neil Jerram
2011-03-30 21:25 ` Andy Wingo
2011-03-30 21:43 ` Andy Wingo
2011-03-30 21:54 ` Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2011-03-30 19:06 Mike Gran
2011-03-30 21:28 ` 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=m3ipv051jt.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=guile-devel@gnu.org \
--cc=ianprice90@googlemail.com \
--cc=neil@ossau.uklinux.net \
/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).