From: Nick Garnett <nickg@ecoscentric.com>
To: Grant Edwards <grant.b.edwards@gmail.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: What causes interrupted network system calls?
Date: Wed, 28 Oct 2009 18:41:00 -0000 [thread overview]
Message-ID: <m3pr872wfj.fsf@xl5.calivar.com> (raw)
In-Reply-To: <hca2pf$11o$1@ger.gmane.org>
Grant Edwards <grant.b.edwards@gmail.com> writes:
> We do have CYGPKG_LIBC_SIGNALS (it comes in with one of the
> network templates), but nobody ever calls raise(), and I'm
> pretty sure nobody ever calls signal() either.
I don't think that package does any real signal handling. It is just
there to provide the minimal signal mechanism required by the C
library. It wouldn't cause these problems.
> Our copy of the network stack is mostly a few years old, so I'm
> going to see if I can build with a current snapshot of the
> FreeBSD net package.
I doubt that there will be much difference, but it is worth a try.
--
Nick Garnett eCos Kernel Architect
eCosCentric Limited http://www.eCosCentric.com The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No: 4422071
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-10-28 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 16:06 [ECOS] " Grant Edwards
2009-10-28 17:02 ` Carruth, Rusty
2009-10-28 17:15 ` [ECOS] " Grant Edwards
2009-10-28 17:53 ` Nick Garnett
2009-10-28 18:05 ` Grant Edwards
2009-10-28 18:27 ` Nick Garnett
2009-10-28 18:40 ` Grant Edwards
2009-10-29 18:34 ` Grant Edwards
2009-10-29 18:53 ` Nick Garnett
2009-10-29 19:04 ` Grant Edwards
2009-10-28 18:33 ` Grant Edwards
2009-10-28 18:41 ` Nick Garnett [this message]
2009-10-28 18:15 ` Carruth, Rusty
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=m3pr872wfj.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=grant.b.edwards@gmail.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).