From: "redsprite" <redsprite@myway.com>
To: linux-c-programming@vger.kernel.org
Subject: SIGIO interrupts poll
Date: Tue, 3 Feb 2004 11:59:40 -0500 (EST) [thread overview]
Message-ID: <20040203165940.CE70839A1@mprdmxin.myway.com> (raw)
I'm working on a large software project and two of the developers have coded each other into a corner.
Specifically, one thread catches SIGIO to read from a hardware device over the serial port. A second thread uses poll() to read from some sockets to other computers.
Independently they work, but when put together the thread that catches SIGIO is preventing the socket-reading thread from getting any of its data.
Is there a way to have the SIGIO handler re-throw the signal so the thread using poll() can catch it?
Andrea
_______________________________________________
No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com
next reply other threads:[~2004-02-03 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 16:59 redsprite [this message]
2004-02-03 22:47 ` SIGIO interrupts poll Glynn Clements
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=20040203165940.CE70839A1@mprdmxin.myway.com \
--to=redsprite@myway.com \
--cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).