From: Ulrich Drepper <drepper@cygnus.com>
To: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: threads & signals
Date: Thu, 19 Aug 1999 16:41:00 -0000 [thread overview]
Message-ID: <m3aerne3x3.fsf@localhost.localnet> (raw)
I've checked in this morning a patch to pass signal contexts to the
signal handlers when using threads. This currently is only in the
development branch since I cannot test whether it works. Those have
threaded applications are called to test whether it breaks anything.
If I don't hear anything negative by tomorrow I'll copy the change
over.
I hope to fix the last reported problem today and then will make a
pre3 release tomorrow or so.
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
reply other threads:[~1999-08-19 16:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3aerne3x3.fsf@localhost.localnet \
--to=drepper@cygnus.com \
--cc=libc-hacker@sourceware.cygnus.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).