From: Marius Vollmer <mvo@zagadka.de>
Cc: Han-Wen Nienhuys <hanwen@xs4all.nl>, guile-devel@gnu.org
Subject: Re: crash on current CVS.
Date: Mon, 06 Jun 2005 21:52:40 +0300 [thread overview]
Message-ID: <87hdgbjp1j.fsf@zagadka.de> (raw)
In-Reply-To: <4278902A.8050902@ossau.uklinux.net> (Neil Jerram's message of "Wed, 04 May 2005 10:04:42 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> Han-Wen Nienhuys wrote:
>> guile> (eval-enable 'foo)
>> throw from within critical section.
>> Geannuleerd
>> muurbloem:~/src/lilypond$
>
> FWIW, I believe this is also covered by a comment that I recently
> added in scm_eval_options_interface.
Yep:
2005-06-06 Marius Vollmer <mvo@zagadka.de>
* eval.c (scm_eval_options_interface): Use
scm_frame_critical_section instead of SCM_CRITICAL_SECTION_START
and SCM_CRITICAL_SECTION_END.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2005-06-06 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 10:48 crash on current CVS Han-Wen Nienhuys
2005-05-04 9:04 ` Neil Jerram
2005-06-06 18:52 ` Marius Vollmer [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=87hdgbjp1j.fsf@zagadka.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
/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).