From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-devel@gnu.org
Subject: Re: Warning: Unstable POSIX threads support comitted to CVS
Date: 09 Dec 2002 15:26:03 +0100 [thread overview]
Message-ID: <ljr8cruv44.fsf@burns.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <xy77kej71dc.fsf@nada.kth.se>
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
> It is very irritating that signals are delivered to whatever thread
> happens to run for the moment.
Do you refer to the execution of POSIX signal handlers or to the
execution of Scheme signal handlers? Scheme handlers are registered
for a particular thread and will always execute in that thread. If
you don't specify a thread, as in (sigaction SIGINT handler), the
handler is registered for the calling thread.
POSIX specifies that a POSIX signal is delivered to a random thread
that has not blocked that signal. On Linux, a thread is really a
process with its own PID and since signals are delivered to a specific
PID, they are in effect delivered to specific threads (or process
groups -> thread groups). For example, a SIGINT handler is executed
in all threads of a process since the whole process group is signalled
by the terminal driver.
That is, signals-plus-threads are quite nasty on Linux. I think we
should have a dedicated signal handling thread that polls for signals
and marks the relevant system asyncs when they arrive.
(More later.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-12-09 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 13:44 Warning: Unstable POSIX threads support comitted to CVS Mikael Djurfeldt
2002-12-09 14:26 ` Marius Vollmer [this message]
2002-12-09 17:40 ` Mikael Djurfeldt
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=ljr8cruv44.fsf@burns.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
--cc=guile-devel@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).