[ECOS] Re: What causes interrupted network system calls?

Nick Garnett nickg@ecoscentric.com
Thu Oct 29 18:53:00 GMT 2009

 Grant Edwards <grant.b.edwards@gmail.com> writes:

> We do have the SNMP agent running, but I didn't find any
> alarm() or raise() calls.  What else can cause a signal in eCos?
> Are signals thread-specific?

If you don't have the POSIX package then there won't be any signal
deliver of the sort that could affect the net stack.

The net stack interprets any return from an event signal that is not a
proper signal or a timeout as an interrupt and returns EINTR. If POSIX
is not included then something else must be forcing that thread out of
the semaphore wait. Perhaps there are other parts of the system that
call cyg_thread_release() and may be zapping the wrong thread. Or
perhaps the right thread at the wrong time.

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

More information about the Ecos-discuss mailing list