From: ludo@gnu.org (Ludovic Courtès)
To: bug-hurd@gnu.org
Cc: guile-user@gnu.org
Subject: Re: Guile not running properly on GNU/Hurd
Date: Sat, 09 Feb 2013 00:41:31 +0100 [thread overview]
Message-ID: <87pq0acr10.fsf@gnu.org> (raw)
In-Reply-To: 20130208221842.GA5689@mail.sceen.net
Richard Braun <rbraun@sceen.net> skribis:
> Actually, it has nothing to do with Mach. What happens is that, when
> catching one of the SIGUSR signals (SIGUSR1 i guess), the process calls
> sigsuspend, waiting for the next (probably SIGUSR2). But when returning
> from the handler (in sigreturn), the sigcontext is NULL, which actually
> makes sigreturn return. This is prohibited, and catched by setting the
> stack frame to run the firewall function (which, by running the hlt
> instruction, causes the SIGILL signal). I guess we could reduce the
> case to a small test unit that calls sigsuspend in a (SA_SIGINFO)
> signal handler and see how it goes, in which case there is a bug in the
> signal handling code.
Perhaps one test would be to #undef SA_SIGINFO in libgc’s
pthread_stop_world.c, and see if the problem still occurs?
Ludo’.
prev parent reply other threads:[~2013-02-08 23:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 18:51 Guile not running properly on GNU/Hurd Gabriel Schnoering
2013-02-02 22:24 ` Richard Braun
2013-02-04 22:09 ` Ludovic Courtès
2013-02-04 22:14 ` Pino Toscano
2013-02-09 9:48 ` Neal H. Walfield
2013-02-04 18:26 ` Gabriel Schnoering
2013-02-08 18:08 ` Gabriel Schnoering
2013-02-08 22:18 ` Richard Braun
2013-02-08 23:41 ` Ludovic Courtès [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=87pq0acr10.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=guile-user@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).