This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: simultaneous socket write/close causes panic?
- From: Gary Thomas <gthomas at ecoscentric dot com>
- To: Grant Edwards <grante at visi dot com>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: 28 Oct 2002 14:38:48 -0700
- Subject: Re: [ECOS] simultaneous socket write/close causes panic?
- References: <20021028153205.A19762@visi.com>
On Mon, 2002-10-28 at 14:32, Grant Edwards wrote:
>
> [using a eCos and network snapshot from Jan 2001]
>
> A customer has reported to me that simultaneously writing and
> closing a socket causes the system to crash with the message
> "PANIC: sbflush". I believe that this error was caused by
> having one thread close a socket while another thread is
> writing data to the socket. He's modified his application to
> avoid conflicting write/close calls.
>
> I haven't been able to find any mention of this problem in the
> mailing list archives...
>
> Is this a known issue?
>
> Is it something worth trying to fix, or is the answer simply
> "don't do that".
a) Don't do that.
b) If it could be reproduced with the new stack, it might be
worth looking at. Otherwise, goto "a"
--
------------------------------------------------------------
Gary Thomas |
eCosCentric, Ltd. |
+1 (970) 229-1963 | eCos & RedBoot experts
gthomas@ecoscentric.com |
http://www.ecoscentric.com/ |
------------------------------------------------------------
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss