From: ludo@gnu.org (Ludovic Courtès)
To: 11776@debbugs.gnu.org
Cc: debian-hurd@lists.debian.org, bug-hurd@gnu.org
Subject: bug#11776: Guile
Date: Thu, 28 Jun 2012 23:20:07 +0200 [thread overview]
Message-ID: <87vcib6smw.fsf@gnu.org> (raw)
In-Reply-To: <4FE7BD78.3010905@gmail.com>
Samuel Thibault <samuel.thibault@gnu.org> skribis:
> I don't know _hurd_setup_sighandler very much and don't have time to
> dive in it, but that's most probably where to look at. Just an idea: is
> guile perhaps using SA_ONSTACK?
Neither Guile nor libgc does, AFAICS.
Ludo’.
next prev parent reply other threads:[~2012-06-28 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 1:23 Guile Cyril Roelandt
2012-06-25 11:00 ` Guile Samuel Thibault
2012-06-26 1:27 ` Guile Cyril Roelandt
2012-06-26 10:26 ` Guile Samuel Thibault
2012-06-28 21:20 ` Ludovic Courtès [this message]
2012-06-25 21:12 ` bug#11783: Guile on GNU/Hurd Ludovic Courtès
2012-06-25 21:13 ` bug#11784: " Ludovic Courtès
2012-07-05 21:31 ` bug#11784: Status: " Andy Wingo
2016-06-20 19:35 ` bug#11776: bug#11784: " Andy Wingo
2012-06-25 21:24 ` bug#11776: Guile Ludovic Courtès
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=87vcib6smw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=11776@debbugs.gnu.org \
--cc=bug-hurd@gnu.org \
--cc=debian-hurd@lists.debian.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).