From: Andy Wingo <INVALID.NOREPLY@gnu.org>
To: Andy Wingo <wingo@pobox.com>, Cedric Cellier <rixed@free.fr>,
bug-guile@gnu.org
Subject: [bug #32436] bugs entering guile from pthreads
Date: Fri, 18 Mar 2011 22:32:45 +0000 [thread overview]
Message-ID: <20110318-223245.sv20118.97665@savannah.gnu.org> (raw)
In-Reply-To: <20110318-210436.sv20118.76867@savannah.gnu.org>
Follow-up Comment #2, bug #32436 (project guile):
If I scm_init_guile, where it used to not clean up, now it fails fast (and
incorrectly).
http://thread.gmane.org/gmane.lisp.guile.bugs/5342
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?32436>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
prev parent reply other threads:[~2011-03-18 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 14:16 [bug #32436] bugs entering guile from pthreads Andy Wingo
2011-02-12 14:17 ` Andy Wingo
2011-03-18 21:04 ` Andy Wingo
2011-03-18 22:32 ` Andy Wingo [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=20110318-223245.sv20118.97665@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=rixed@free.fr \
--cc=wingo@pobox.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).